Systems and methods for indicating real time availability of key assemblies for user input to an information handling system

ABSTRACT

Systems and methods are disclosed that may be implemented to indicate real time availability of individual key assemblies for user input to an information handling system. In one embodiment, the disclosed systems and methods may be implemented to retract an individual key assembly of a user input device (e.g., such as keyboard matrix, game controller, game pad, computer mouse, etc.) when the key assembly is, or becomes, unavailable for input to a user application (e.g., such as a computer game) that is executing on a host programmable integrated circuit (e.g., such as host CPU) of an information handling system. Such a retracted key assembly may then be extended when it becomes available for input to the user application.

RELATED APPLICATIONS

This patent application is a continuation-in-part of U.S. patent application Ser. No. 15/418,120, titled “SYSTEMS AND METHODS FOR IMPLEMENTING RETRACTABLE AND/OR VARIABLE DEPRESSION FORCE KEY ASSEMBLIES,” by Mark A. Casparian, et al., filed on Jan. 27, 2017, which is incorporated herein by reference in its entirety. This patent application is also a continuation-in-part of U.S. patent application Ser. No. 15/418,232, titled “RETRACTABLE AND/OR VARIABLE DEPRESSION FORCE KEY ASSEMBLIES AND METHODS FOR USING THE SAME,” by Mark A. Casparian, et al., filed on Jan. 27, 2017, which is incorporated herein by reference in its entirety.

FIELD

This application relates to key assemblies, and more particularly to key assemblies and methods for using the same.

BACKGROUND

As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.

Many computer games provide the player with actions (abilities) and consumables (resources) with restricted availability. For example, some game actions can only be performed with restricted frequency (e.g., once every certain number of seconds). Similarly, some resources are provided to the player in a restricted amount (e.g., 12 grenades or 5 blue potions). The availability and amount of these actions and resources are represented within the game's interface displayed on the computer display, often at the periphery of the player's view. For example, when an action is performed, it becomes unavailable for a certain number of seconds. After this “cool-down” period has elapsed, the action is made available again. In order to keep track of the availability of an action, the player must watch the timer graphic, count down the “cool-down” time in their head, or repeatedly hit the key corresponding to the desired game action knowing that the action will eventually be available and ready for use again. All of these activities require the user's attention and effort that could be applied elsewhere to greater benefit.

Mechanisms for the provision of haptic feedback to vibrate an entire game controller have been employed with computer games to convey game actions taken against the player during gaming by other players (being hit with a bullet) or by the environment (a bumpy road).

Mechanical technologies exist in non-computer fields that provide mechanical lockouts, like pistols (slide held rear-ward and trigger locked when magazine and chamber are empty). Most nail-guns provide a catch mechanism, a safety feature that locks the trigger button until the catch release is held into contact with and compressed against a surface. Player pianos mechanically lock piano keys arranged in heavily pre-scripted sequences.

SUMMARY

Systems and methods are disclosed herein that may be implemented to indicate real time availability of individual key assemblies for user input to an information handling system. In one embodiment, the disclosed systems and methods may be implemented to retract an individual key assembly of a user input device (e.g., such as keyboard matrix, game controller, game pad, computer mouse, etc.) when the key assembly is, or becomes, unavailable for input to a user application (e.g., such as a computer game) that is executing on a host programmable integrated circuit (e.g., such as host CPU) of an information handling system. Such a retracted key assembly may then be extended when it becomes available for input to the user application. In one exemplary embodiment, software and/or firmware components executed by one or more programmable integrated circuits of an information handling system and/or a user input device for such a system may be orchestrated to control key assembly extension and retraction based on monitored user input availability from individual key assemblies to an executing user application, e.g., by monitoring computer game “cool-down” periods, computer game in-game events and status (e.g., resource status), etc. In this way, the orchestrated software components may be executed to cause retraction and extension of key assemblies in real-time as may be appropriate for a given user application (e.g., given computer game) and/or set of user preferences input by a user. Thus, in one embodiment an orchestration of software and/or firmware may monitor cool-downs and resources for a computer game, retracting and extending keys in real-time as appropriate for a given game or set of player preferences.

In one exemplary embodiment, a given key assembly of a user input device that is coupled to an information handling system may be held in a retracted position for a period of time that its ability or resource associated with an executing user application is unavailable. The given key assembly may then be extended to accept user input when that period of time is up. In this way, a user may be apprised and kept informed of the real time availability of a given individual key assembly for input to a user application (e.g., during computer game play) by merely touching the key assembly to ascertain and monitor the extended or retracted state of the given key assembly, e.g., without the distraction of conventional methods, such as watching a timer graphic, counting the “cool-down” time in their head, or repeatedly pressing the given key until the application responds again to input from the key assembly. In the exemplary case of a computer gaming environment, active feedback regarding action/item availability may be so provided in a manner that is more useful to players and creates greater availability awareness than conventional techniques.

Any suitable methodology and/or apparatus may be employed to implement key assembly retraction do indicate real time availability of individual key assemblies for user input. However, in one exemplary embodiment, retractable key assemblies that include one or more electro-permanent magnets (EPMs) together with permanent magnet and/or magnetically permeable (e.g., ferromagnetic) key assembly components may be employed to control retraction and extension of individual key assemblies to indicate real time availability of an individual key assembly. Such key assembly components may also be utilized to control peak depression force (e.g., typing force) required to depress and displace a key assembly from an extended position to a lower position that causes the key assembly to produce a digital or analog output signal, e.g., to a keyboard controller. In embodiments of the disclosed systems and methods, the state of an external magnetic field of key assembly EPMs may be controlled (e.g., selectably turned ON, turned OFF, varied in polarity direction, and/or varied in strength) by temporary application of a current pulse having an appropriate strength and/or polarity to a conductive coil of a given keyboard assembly EPM to cause magnetic material of the EPM to emit a magnetic field of desired strength and/or polarity that in turn causes the desired key retraction and/or peak key depression force result. Using the disclosed systems and methods, energy consumption is reduced since EPMs only require a temporary electrical current pulse be applied to the EPM coil to select and establish the desired strength of the EPM magnetic field (or to switch the EPM magnetic field ON and OFF), but require no further application of electrical current to hold or maintain the state or strength of the magnetic field emitted by the EPM magnetic material once such state or strength has been so established by application of the temporary current pulse to the EPM coil.

In one exemplary embodiment, a key assembly may be provided alone or part of multiple similar key assemblies of a keyboard matrix. The key assembly may employ an EPM to selectably emit a magnetic field that acts on a magnetically permeable (e.g., ferromagnetic) body of the key assembly, and may be configured such that when the EPM is turned ON it emits a magnetic field that attracts the magnetically permeable body so as to cause the magnetically permeable body to bias the key assembly upward into an extended position, and such that when the EPM is turned OFF the key assembly is biased downward into a retracted position by a downward bias force. Such a downward bias force may be applied, for example, by a spring, a permanent magnet, another separate EPM, etc. In embodiments where a spring or another magnet are used for the downward bias force, the key assembly may be configured such that the downward bias force is less than the minimum upward bias force provided by the EPM when its magnetic field is turned ON. In one embodiment, upward bias applied by at least one EPM to an extended key assembly may be varied (e.g., by varying the time duration or amplitude of current pulses applied to the EPM, by varying the number of EPMs that are simultaneously turned ON to bias the key assembly in the upward position, etc.). By so varying the upward bias applied to an extended key assembly, the required user force to overcome the upward bias force and depress the key assembly downward may be varied.

In another exemplary embodiment, retraction and/or depression force of one or more key assemblies may be controlled and operated using a combination of software, custom application programming interface (API) and key assembly and programmable integrated circuit hardware. In one such an embodiment, a combination of a key retraction profile configurator application and an intervening API may be employed to communicate with a set of software-controlled EPMs that are mechanically configured to cause extension and retraction of key assemblies, and/or to control depression force required by a user to depress individual key assemblies. Such a key retraction profile configurator application may be employed in one embodiment to create user configurable key map information in the form of a unique user configurable application key map file for a given user application in focus (e.g. such as a given computer game). Such a given user application in focus (e.g. such as a given computer game) specifies that all keys used by the given user application are to stay raised or extended, and all other keys not used by the user application are to remain retracted, while the given user application remains in focus.

In a further embodiment, a key retraction profile configurator application may be further provided that allows a user to create custom application profiles (e.g., such as custom computer game profiles for each different application or instance of in-focus application) and/or to load application profiles directly from an application in focus (e.g., such as an application profile written by developers of the application). Such an application profile may include a listing of all the key assemblies that are usable in the application for various commands, an amount of downward finger force (peak or maximum depression force) to overcome upward key assembly bias and cause downward movement of a given key assembly to cause key actuation and output of digital or analog key signal. This application profile information may be communicated to the hardware layer (e.g., including a keyboard controller) via a custom API where the application key identities and peak force parameters per key may be stored for the application that has been loaded and is focus.

It will be understood that peak key assembly depression force may be varied in any suitable manner. For example, multiple EPMs may be provided for each individual key assembly so as to support the ability to incrementally increase the amount of finger force (peak depression force) required for the “make actuation” of the key assembly switch, thus providing a software-controllable technique to allow a user to configure the desired finger force desired on a key assembly-by-key assembly basis. Discrete force levels may also be achieved in one embodiment. In another embodiment a permanent magnet (e.g., aluminum-nickel-cobalt or AlNiCo) in an EPM assembly may be partially magnetized to achieve any desired peak depression force between two different peak depression endpoints. In one embodiment, such partial magnetization may be achieved by varying the voltage of a current pulse applied to the coil of an EPM assembly to generate a temporary magnetic field. In this regard, the generated magnetic field of an EPM coil needs to be greater than the existing coercive force of the EPM magnet material in order to change the residual magnetization of the EPM. Thus, as the generated magnetic field of the EPM coil increases above the coercive force of EPM magnet material, the amount of residual magnetization goes up until the EPM magnet material reaches a fully saturated state.

In another exemplary embodiment, multiple retractable keys of a keyboard matrix array may be individually actuated by electro-permanent magnets that are controlled using retractable key control circuitry and high voltage and current pulses. The retractable key control circuitry may be configured to implement a matrix addressing scheme to individually address the electro-permanent magnet of each key with a high voltage and current pulse of selected polarity (direction) to either retract or extend the selected key. The matrix addressing scheme may include binary decoders coupled to control pairs of Half-H bridge drivers that separately supply high voltage and current pulses of selected polarity to each of the electro-permanent magnets of the individual keys to cause retraction or extension of each key. To control retraction or extension of each key, a microcontroller or other programmable integrated circuit may implement an electronic programming module to provide a current direction control signal, as well as provide the key row address to a row binary decoder and the key column address to a column binary controller. The row and column binary decoders in turn provide chip enable signals to two respective Half-H bridge drivers that correspond to the row and column of the selected key. The direction of current causes magnetic field of the electro-permanent magnets to vary in order to control key retraction and extension. To limit current drawn, the retractable key control circuitry may be configured to actuate only one key of the keyboard matrix at a time, e.g., in round robin fashion. Fault detection and feedback circuitry may be included to provide a feedback signal to the microcontroller that is indicative of a fault detected by the Half-H bridge drivers.

The disclosed systems and methods may be implemented in one exemplary embodiment to enable users (e.g., such as PC Gamers) the ability to configure their keyboard such that only the key assemblies mapped and in use by a user application (e.g., such as a particular computer game) are available for use (for depression and input) while all other key assemblies not used by the application are automatically retracted down and out of position such as to not be accidentally pressed while at the same time their respective scan codes may be optionally blocked from being reported to the OS. Alternatively or additionally, the disclosed systems and methods may be implemented to allow a user to adjust the amount of finger force (or peak depression force) required for the “make actuation” point on a key assembly-by-key assembly basis, or for a select group of multiple key assemblies so as to help prevent accidental pressing of critical in-game key assembly buttons, e.g., such as an in-game electromagnetic pulse (EMP) Blast. In one embodiment, a key assembly may be programmed with a greater peak depression force in order to require the key assembly to be pressed with a greater finger force for typing than are all other keys (thus requiring a deliberate press versus accidentally brushing up against the corner of a keycap of a key assembly and inadvertently pressing it).

In one respect, disclosed herein is an information handling system, including: at least one programmable integrated circuit programmed to execute an operating system and to execute at least one in-focus user application on the information handling system; one or more depressible key assemblies, each of the key assemblies coupled to provide an output signal when depressed by a user and having an extended position and a retracted position that is selected in response to a control signal; at least one programmable integrated circuit coupled to receive the output signals provided by each of the depressible key assemblies and coupled to provide corresponding input signals to the operating system based on the output signals provided by each of the depressible key assemblies; and at least one programmable integrated circuit coupled to provide the control signal to control a height of at least one given key assembly between the extended position and the retracted position while the user application is executing based on real time availability of at least one ability or resource of the in-focus application that is associated with the given key assembly.

In another respect, disclosed herein is a method of operating an information handling system. The method may include at least one programmable integrated circuit of the information handling system to: execute an operating system and to execute at least one in-focus user application on the information handling system; receive output signals from one or more depressible key assemblies when depressed by a user, and provide corresponding input signals to the operating system based on the output signals received from the depressible key assemblies; and provide a control signal to control a height of at least one given one of the key assemblies between the extended position and the retracted position while the user application is executing based on real time availability of at least one ability or resource of the in-focus application that is associated with the given key assembly.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of a portable information handling system according to one exemplary embodiment of the disclosed systems and methods.

FIG. 2A illustrates a perspective view of a portable information handling system according to one exemplary embodiment of the disclosed systems and methods.

FIG. 2B illustrates a perspective view of a portable information handling system according to one exemplary embodiment of the disclosed systems and methods.

FIG. 2C illustrates a perspective view of a portable information handling system according to one exemplary embodiment of the disclosed systems and methods.

FIG. 2D illustrates a perspective view of a portable information handling system according to one exemplary embodiment of the disclosed systems and methods.

FIG. 2E illustrates an overhead view of an external keyboard according to one exemplary embodiment of the disclosed systems and methods.

FIG. 2F illustrates an overhead view of a game controller according to one exemplary embodiment of the disclosed systems and methods.

FIG. 2G illustrates an overhead of a mouse according to one exemplary embodiment of the disclosed systems and methods.

FIG. 3 is a block diagram showing interrelation of various logic and hardware layers of an information handling system according to one exemplary embodiment of the disclosed systems and methods.

FIG. 4A illustrates a side cross section view of a retractable key assembly according to one exemplary embodiment of the disclosed systems and methods.

FIG. 4B illustrates a side cross section view of a retractable key assembly according to one exemplary embodiment of the disclosed systems and methods.

FIG. 4C illustrates an overhead perspective view of a retractable key assembly according to one exemplary embodiment of the disclosed systems and methods.

FIG. 4D illustrates an underside perspective view of a retractable key assembly according to one exemplary embodiment of the disclosed systems and methods.

FIG. 5A illustrates a side cross section view of a retractable key assembly according to one exemplary embodiment of the disclosed systems and methods.

FIG. 5B illustrates a side cross section view of a retractable key assembly according to one exemplary embodiment of the disclosed systems and methods.

FIG. 5C illustrates an overhead perspective view of a retractable key assembly according to one exemplary embodiment of the disclosed systems and methods.

FIG. 5D illustrates an underside perspective view of a retractable key assembly according to one exemplary embodiment of the disclosed systems and methods.

FIG. 6A illustrates a side cross section view of a retractable key assembly according to one exemplary embodiment of the disclosed systems and methods.

FIG. 6B illustrates a side cross section view of a retractable key assembly according to one exemplary embodiment of the disclosed systems and methods.

FIG. 6C illustrates an overhead perspective view of a retractable key assembly according to one exemplary embodiment of the disclosed systems and methods.

FIG. 6D illustrates an underside perspective view of a retractable key assembly according to one exemplary embodiment of the disclosed systems and methods.

FIG. 7 is a flow chart illustrating interaction between layers of an information handling system according to one exemplary embodiment of the disclosed systems and methods.

FIG. 8 is a block diagram showing circuit components of an information handling system according to one exemplary embodiment of the disclosed systems and methods.

FIG. 9A is a block diagram showing circuit components of an information handling system according to one exemplary embodiment of the disclosed systems and methods.

FIG. 9B is a block diagram showing circuit components of an information handling system according to one exemplary embodiment of the disclosed systems and methods.

FIG. 9C is a block diagram showing circuit components of an information handling system according to one exemplary embodiment of the disclosed systems and methods.

FIG. 10 illustrates a flow chart of methodology according to one exemplary embodiment of the disclosed systems and methods.

FIG. 11 illustrates a flow chart of methodology according to one exemplary embodiment of the disclosed systems and methods.

FIG. 12 illustrates a flow chart of methodology according to one exemplary embodiment of the disclosed systems and methods.

FIG. 13 illustrates a flow chart of methodology according to one exemplary embodiment of the disclosed systems and methods.

DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

FIG. 1 is a block diagram illustrating a portable information handling system 100 as it may be configured to according to one exemplary embodiment of the disclosed systems and methods. In one embodiment, portable information handling system 100 may be a battery-powered portable information handling system that is configured to be optionally coupled to an external source of system (DC) power, for example AC mains and an AC adapter. Information handling system may also include an internal DC power source 137 (e.g., smart battery pack and power regulation circuitry) that is configured to provide system power source for the system load of information handling system, e.g., when an external source of system power is not available or not desirable. Portable information handling system 100 may be, for example, a notebook or laptop computer, tablet computer, convertible computer, etc. and may be configured with a chassis enclosure delineated as shown by the outer dashed outline.

However, it will be understood that the disclosed systems and methods may be implemented in other embodiments for other types of portable information handling systems that include or are coupled to a separate peripheral keyboard matrix or other peripheral input device such as mouse, game controller, etc. For example, the disclosed systems and methods may be implemented with an AC-powered or non-portable desktop computer or a computer workstation that is coupled to an external keyboard, mouse or game controller that itself includes key assembly components 405 with EPMs 197 and optionally one or more of keyboard controller 121 and/or decode and bridge driver circuitry 195 components described further herein. Alternatively one or more of such keyboard controller 121 and/or decode and bridge driver circuitry 195 components may be instead implemented within a non-portable desktop or computer workstation information handling system chassis that is coupled to the EPMs 197 of the key assemblies 405. Further information on non-portable or non-battery powered information handling system architecture and components may be found in United States Patent Application Publication Number 20140281618A1, which is incorporated herein by reference in its entirety. It will also be understood that the particular configuration of FIG. 1 is exemplary only, and that an information handling system may be configured with fewer, additional or alternative components than those illustrated and described herein.

As shown in FIG. 1, information handling system chassis 100 of this exemplary embodiment includes various integrated components that are embedded on a system motherboard 139, it being understood that any one or more of such embedded components may be alternatively provided separate from motherboard 139 within a chassis case 100 of a portable information handling system, e.g., such as provided on a daughter card or other separate mounting configuration. As further shown, a host programmable integrated circuit 105 is provided, e.g., as a central processing unit CPU such as an Intel Haswell processor, an Advanced Micro Devices (AMD) Kaveri processor, or one of many other suitable programmable integrated circuits currently available. In this embodiment, a host programmable integrated circuit in the form of CPU 105 may execute a host operating system (OS) for the portable information handling system. System memory may include main system memory 115 (e.g., volatile random access memory such as DRAM or other suitable form of random access memory) coupled (e.g., via DDR channel) to an integrated memory controller (iMC) 117 of host programmable integrated circuit 105 to facilitate memory functions, although it will be understood that a memory controller may be alternatively provided as a separate chip or other circuit in other embodiments. Not shown is optional nonvolatile memory (NVM) such as Flash, EEPROM or other suitable non-volatile memory that may also be coupled to host programmable integrated circuit 105.

As shown in FIG. 1, host programmable integrated circuit 105 itself includes an integrated GPU (iGPU) 109 and portable information handling system chassis 100 may also include an optional separate internal discrete GPU (I-dGPU) 120. In one mode of operation, video content from CPU 105 may be sourced at any given time either by iGPU 109 or I-dGPU 120. Further information on integrated and discrete graphics maybe found, for example, in United States Patent Application Publication Number 20160117793A1, which is incorporated herein in its entirety for all purposes. It will be understood that PCI-e is just one example of a suitable type of data bus interface that may be employed to route graphics data between internal components within portable information handling system chassis 100.

As further illustrated in FIG. 1, host programmable integrated circuit 105 may be coupled to embedded platform controller hub (PCH) 110 which may be present to facilitate input/output functions for the host programmable integrated circuit 105 with various internal components of information handling system 100. In this exemplary embodiment, PCH 110 is shown coupled to other embedded components on a motherboard 139 that include system embedded controller 103 (e.g., used for real time detection of events, etc.), non-volatile memory 107 (e.g., storing BIOS, etc.), wireless network card (WLAN) 153 for Wi-Fi or other wireless network communication, integrated network interface card (LAN) 151 for Ethernet or other wired network connection, touchpad microcontroller (MCU) 123, keyboard microcontroller (MCU) 121, audio codec 113, audio amplifier 112, and auxiliary embedded controller 111 which may be implemented by a microcontroller. Also shown coupled to PCH 110 are other non-embedded internal components of information handling system 100 which include integrated display 125 (e.g., LCD or LED flat panel display integrated into notebook computer lid or tablet, or other suitable integrated portable information handling system display device), audio endpoint in the form of internal speaker 119, integrated keyboard and touchpad 145, and storage 135 which may be a local hard drive storage or other suitable type of system storage including solid state drive (SSD), optical drive/s, NVRAM, Flash or any other suitable form of internal storage.

Also shown in FIG. 1 is keyboard controller 121 that may be coupled to receive digital output signals 732 from individual key assemblies 405 (e.g., momentary on digital keys) of keyboard matrix 199 when depressed by a user, and to provide corresponding keyboard output signals (e.g., in the form of scan code signals 736) corresponding to individual depressed digital keys of keyboard matrix 199 to an appropriate device driver 316 (e.g., PS2 keyboard device driver) executing on host programmable integrated circuit 105 via PCH 110. Keyboard controller 121 may poll all the momentary on digital keys in the keyboard matrix 199 and broadcast a scan code output corresponding to any pressed keys to the operating system (OS) 354 of information handling system 100. It will be understood that in other embodiments, other types of retractable key assemblies of a keyboard matrix 199 (e.g., variable pressure or variable displacement key assemblies, etc.) and/or tasks of controller 110 may be implemented by auxiliary embedded controller 111 or other programmable integrated circuit, rather than by a separate microcontroller 121. Keyboard controller 121 may also be configured as shown to control individual electro-permanent magnets (EPMs) 197 via addressed key assembly control signals 734 (e.g., general purpose input/output signals) provided to decode and bridge driver circuitry 195, which in turn provides current pulses 450 to selected EPMs 197 that are configured to cause mechanical retraction or extension of individual keys of keyboard matrix 199 in a manner that will be described further herein. Further information on possible tasks and features of keyboard controller 121 may be found illustrated and described in U.S. Pat. Nos. 8,411,029; and 9,272,215, each of which is incorporated herein by reference in its entirety for all purposes.

Although in one embodiment keyboard controller 121 receives digital output (e.g., momentary on) signals from key assemblies 405, it will be understood that in retractable key assemblies 405 may alternatively or additionally produce analog (e.g., variable pressure or variable displacement) output signals that are provided to a keyboard controller 121 or other programmable integrated circuit, such as auxiliary embedded controller 111 or other device. Examples of production and processing of analog output signals may be found in U.S. Pat. Nos. 8,674,941; 8,700,829; 9,343,248; and 9,111,005, each of which is incorporated herein by reference in its entirety for all purposes.

The tasks and features of auxiliary embedded controller 111 may optionally include, but are not limited to, controlling various possible types of optional non-graphics light sources 252 based on multi-channel audio information produced by a computer game (or any other type of sound-generating computer application of application layer 143) executing on CPU 105. For example, auxiliary embedded controller 111 may be optionally configured to communicate lighting control signals to an optional light driver chip 122 to control lighting colors, luminance level and effects (e.g. pulsing, morphing). A light driver chip 122 may be in turn coupled directly via wire conductor to drive light sources 252 (e.g., RGB LEDs such as Lite-On Technology Corp part number LTST-008BGEW-DF_B-G-R or other suitable lighting elements) based on the lighting control signals received from auxiliary EC 111 or MCU 121 as the case may be. Examples of lighting control technology and techniques that may be utilized with the features of the disclosed systems and methods may be found, for example, in U.S. Pat. Nos. 7,772,987; 8,411,029; 9,272,215; U.S. patent application Ser. No. 14/182,647 filed Feb. 18, 2014, U.S. Pat. No. 9,368,300, and U.S. patent application Ser. No. 15/223,613, filed Jul. 29, 2016, each of which is incorporated herein by reference in its entirety for all purposes.

As further shown in FIG. 1, persistent storage (e.g., non-volatile memory) may be additionally coupled to PCH 110, system EC 103, keyboard controller 121 and/or auxiliary EC 111. Such persistent storage may store or contain firmware or other programming that may be used by EC 103 and/or EC 111 to implement one or more user-defined system configurations such as keyboard key retraction options, keyboard lighting options, display lighting options, audio output settings, power management settings, performance monitoring recording settings, designated keyboard macros and/or variable pressure key settings and/or macros, for example, in a manner such as described in U.S. Pat. Nos. 7,772,987; 8,700,829 ,8,411,029; 9,272,215; U.S. patent application Ser. No. 14/182,647 filed Feb. 18, 2014, and U.S. Pat. No. 9,368,300, each of which is incorporated herein by reference in its entirety. In one example illustrated in FIG. 1, dedicated non-volatile memory 127 may be directly coupled to auxiliary EC 111 for this purpose as shown.

As shown in FIG. 1, host programmable integrated circuit 105 may be optionally programmed to execute an audio engine 147 to process multi-channel audio data stream from application layer 143 to produce multi-channel audio information that may be further processed and provided as lighting event command signals from CPU 105 to auxiliary controller 111 in a manner such as described in U.S. patent application Ser. No. 15/223,613 filed Jul. 29, 2016, which is incorporated herein by reference in its entirety for all purposes. Auxiliary controller 111 may in turn produce lighting control signals for light driver chip 122 based on the lighting event command signals provided from host programmable integrated circuit 105.

FIG. 2A illustrates one embodiment of a portable information handling system 100 as it may be configured in one exemplary embodiment with a keyboard matrix 199 having multiple retractable key assemblies 405. It will be understood that FIG. 2A is exemplary only and that a variety of information handling systems or peripherals thereof may be provided with one or more retractable key assemblies 405 that are actuated by EPMs 197 in a manner as described herein, e.g., including peripherals having retractable key assemblies such as external keyboards, mice, game controllers, game pads, etc. In this regard, a retractable key assembly 405 as described herein includes, for example, retractable key assemblies 405 that are employed key assemblies in external keyboards such as illustrated in FIG. 2E, as game controller buttons such as illustrated in FIG. 2F, mouse buttons such as illustrated in FIG. 2G, etc. In this regard, FIG. 2F illustrates one exemplary embodiment of a game controller 250 having retractable key assemblies 405 which may be selectably extended and retracted in a manner as described herein for providing particular signal outputs and/or macro signal outputs for a given user application when depressed, as well as joysticks 251, D-pad 253, and conventional buttons 255. FIG. 2G illustrates one exemplary embodiment of a gaming mouse 260 having retractable key assemblies 405 which may be selectably extended and retracted in a manner as described herein for providing particular signal outputs or macro signal outputs when depressed, as well as mouse wheel 263, and optional conventional left/right mouse buttons 262.

In the embodiment of FIG. 2A, system 100 includes a chassis base component 202 that is hingeably coupled to an integrated display 125 of a chassis lid component 204. As shown, keyboard 199 may be configured with retractable key assemblies 405 having keycaps 404 arranged in a QWERTY layout, although any other arrangement of one or more retractable key assemblies 405 is possible. In FIG. 2, some key assemblies 405 (with keycaps 404) of keyboard matrix 199 are in a mechanically extended position 210 of greater height relative to the keyboard matrix 199 while the remaining key assemblies 405 (with keycaps 404) of keyboard matrix 199 are in retracted condition 211 of a lower height relative to the keyboard matrix. As will be described further herein, selected individual key assemblies of keyboard matrix 199 may be controlled to selectively extend and retract key assemblies 405 with their keycaps 404, e.g., according to user commands, user-created application key map files, application key map files from an application 143 executing on a host programmable integrated circuit 105, real time (in-application) key retraction and/or extension commands from a user application 143, from logic executing on keyboard MCU 121, or from any other type or combination of programmable integrated circuit of information handling system 100.

FIGS. 2B-2D illustrate one exemplary embodiment of how key retraction may be used to provide real time indication of key assembly availability to user of the exemplary portable information handling system 100 of FIG. 2A. In FIG. 2B, all of key assemblies 405 (with keycaps 404) of a QWERTY keyboard matrix 199 start in a mechanically extended position 210 that indicates that all key assemblies 405 are available for user input to a user application 143 that in this example is a computer game executing on system 100. The key assembly condition of FIG. 2B may occur, for example, at the start of a given game session. To reduce clutter in FIG. 2B, only representative key assemblies 405 are labelled “210”, however from the relative position of keycaps 405 it may be seen that all key assemblies 405 are in extended (upward) position in FIG. 2B. It will be understood that in other embodiments, only a subset of the key assemblies 405 of matrix 199 may be initially placed in a mechanically extended position 210, as shown in FIG. 2A.

Still referring to FIG. 2B, some extended key assemblies 405 may have a limited availability policy for user input while application 143 is executing on system 100. In the illustrated embodiment, such key assemblies of limited availability include those labelled Q, W, R and G, while all the remaining key assemblies 405 of matrix 199 have unlimited availability during execution of application 143 (i.e., they remain active for accepting user input and in a mechanically extended position when not depressed by a user). In an alternative embodiment only a portion of the key assemblies 405 of matrix 199 may be initially placed in mechanically extended position 210 and made available for use for the executing application 143 (e.g., such as illustrated in FIG. 2A). In such a case, then the key assemblies 405 having unlimited availability will be the remaining key assemblies 405 that are initially extended and available for the given application 143 that do not have a limited availability policy.

Now, assuming that the application executing on system 100 of FIG. 2B is a first person shooter computer game, key assemblies Q, W and R may each be assigned to a given user ability (e.g., super speed, force field shield, plasma cannon, laser pistol, etc.), while key assembly G may be assigned to a given game resource of specific number or amount (e.g., grenades, bullets, throwing knives, health, etc.). For example, key assembly Q may be assigned to accept user input to shoot a plasma cannon, key assembly W may be assigned to accept user input to shoot a laser pistol, key assembly R may be assigned to accept user input to activate a player force field shield, and key assembly G may be assigned to accept user input to throw a grenade. In this example, the Q, W and R key assemblies would, once pressed by a user, remain retracted and inactive until an associated cool-down timer is complete before extending again for use. The G key assembly will only be active and extended when grenades are available in the player's inventory and will retract and be unavailable for user input when the user runs out of grenades. If the user leaves their hand positioned in place over one or more of key assemblies Q, W, R and G (i.e., a standard user behavior), then the user will know by touch of an extended key assembly the very instant at which one of the game abilities (in this case cannon, laser, shield, grenades) is available for use, without looking away from the main action on screen. This capability may be implemented to provide a huge advantage in single-player, multiplayer and competitive play.

It will be understood that the above-listed examples of abilities and resources are exemplary only, and that availability of other types of abilities and/or resources may be similarly indicated by extension and retraction of key assemblies 405 during execution of a given user application 143. Moreover, real time key availability may be indicated by the disclosed systems and methods for user input to types of applications other than computer games, e.g., content creation tools such as Adobe Creative Suite. For example, particular key assemblies 405 corresponding to different abilities (e.g., tools) of a tool palette from an executing content creation application 312 may be extended or retracted in real time as the respective corresponding abilities (e.g., tools) of the content creation application 312 are enabled or disabled (e.g., depending on what user interface mode the user is currently in). Similarly, particular key assemblies 405 may be extended in real time to indicate what additional abilities (e.g., optional or add-in features of a software application) may be available for use or may be retracted in real time to indicate those additional abilities (e.g., features or capabilities) that are not defined, e.g., depending if certain plugins have been installed or not.

To further illustrate how these limited input availability key assemblies may function during game play, assume that each of key assemblies Q, W and R have a limited user input availability that is defined by a minimum period of time between successive uses, while key assembly G has a limited user input availability that is defined by a cumulative use limit that corresponds to the cumulative number of user input events that have occurred. For example, plasma cannon of key assembly Q may become inactive after its use and must “cool down” for a period of one minute, laser pistol of key assembly W may become inactive after its use and must “cool down” for a period of 30 seconds. Similarly force field shield of key assembly R may become inactive after its use before it becomes inactive and must recharge for a period of one minute. Also, assume that the cumulative number of available grenades that may be thrown during a given game session is limited to the number of grenades in the user's game inventory so that key assembly G may only be depressed a cumulative number of time by a user (to throw one grenade at a time) that corresponds to the number of available grenades at any time.

FIG. 2C illustrates the in-game condition of retractable key assemblies 405 of portable information handling system 100 of FIG. 2A after each of key assemblies Q, W, R and G have been placed in mechanically retracted position 211 and rendered unavailable (and inactive for accepting user input) during a given game session according to the particular limited availability policy defined for the corresponding key assembly for the currently executing user application 143. For example, each of key assemblies Q and W are shown retracted and temporarily unavailable during “cool down” time periods of respective plasma cannon and laser pistol that have occurred just after use of these key assemblies Q and W, and key assembly R is shown retracted and temporarily unavailable during a recharging time period of the force field shield that has occurred just after use of key assembly R. Key assembly G is shown retracted and unavailable after all grenades in the user's game inventory have been used.

FIG. 2D illustrates the in-game condition of retractable key assemblies 405 of portable information handling system 100 of FIG. 2A after each of key assemblies Q, W, R are once again available and placed in mechanically extended position 210 after expiration of its corresponding respective cool down or recharge time period in the same game session as FIG. 2C. However, key assembly G remains unavailable and in mechanically retracted position 211 in this case since the user's grenade inventory has not been replenished and no grenades are currently available for use.

FIG. 2E illustrates one embodiment of an external keyboard 230 such as may be employed for input via communication path 293 (e.g., USB cable or alternatively a wireless communication path) to a host information handling system such as desktop computer or computer work station. Such an external keyboard 230 may in one embodiment include a keyboard microcontroller (MCU) integrated within the body or chassis 290 of the external keyboard 230 that is coupled to host programmable integrated circuit (e.g., CPU) by communication path 293. In FIG. 2E, those key assemblies 405 that are hatched have been retracted in real time to a mechanically retracted position 211 to indicate unavailability of an ability, resource or other function associated with user input by the retracted key assemblies 405.

FIG. 2F illustrates one embodiment of game controller 250 that may be utilized to provide input to a host programmable integrated circuit of a game console. In FIG. 2F, one game controller button 405 has been retracted in real time to mechanically retracted position 211 to indicate unavailability of an ability, resource or other function associated with user input by the retracted game controller button 405.

FIG. 2G illustrates one embodiment of a computer mouse 260 that may be utilized to provide input to a host programmable integrated circuit of an information handling system such as notebook or desktop computer. In FIG. 2F, one hatched mouse button 405 has been retracted in real time to a mechanically retracted position 211 to indicate unavailability of an ability, resource or other function associated with user input by the retracted mouse button 405.

FIG. 3 illustrates a block diagram that shows interrelation of various logic and hardware layers of an information handling system 100 according to one exemplary embodiment of the disclosed systems and methods. As shown in FIG. 3, each of an application layer 350, middleware layer 352, and operating system (OS) layer 354 may be executing on a processor such as host programmable integrated circuit 105 or any other suitable one or more programmable integrated circuits such as controller, microcontroller, microprocessor, ASIC, programmable logic device “PLD” such as FPGA, complex programmable logic device “CPLD”, etc. As further shown, OS layer 354 may be coupled to components of hardware layer 302 that are responsible for controlling retractable key assemblies 405 of keyboard matrix 199 based on commands received through the OS layer 354, and for receiving digital output signals 732 from individual key assemblies of keyboard matrix 199 when depressed by a user.

Referring to FIG. 3 in further detail, application layer 350 may include multiple user applications 312 such as one or more Windows-based or other OS type of computer games (e.g., first person shooter games and other types of shooter games, fighting games, stealth games, platform games, role playing games, etc.). Non-gaming types of applications 312 may also or alternatively be executing in application layer 350, including Windows-based or other OS type of word processing applications, spreadsheet applications, media player applications, web browser applications, etc. As shown, application layer 350 may also include a key retraction profile configurator application 310 (e.g., present as a stand-alone retractable key configurator application or may be executing as part of a game profile configurator application or control center application such as the Alienware Command Center “AWCC” and “AlienFX Plug-In”, both available from Dell Products L.P. of Round Rock, Tex.). Further information on control center applications such as gaming control centers may be found, for example, in U.S. Pat. Nos. 9,111,005, 7,772,987, and United States Patent Application Publication No. 20160117793, each of which is incorporated herein by reference in its entirety.

As described further herein, key retraction profile configurator application 310 may identify or select at least a portion of the retractable key assemblies 405 of keyboard matrix 199 that are to be extended and active at any time for accepting user input for a given user application 312 that is currently in focus on system 100, and/or may select peak depression force level for individual key assemblies 405. Key retraction profile configurator application 310 may make one or both of these selections, for example, based on application key information 770 (e.g., an application key map file designating a portion of the available key assemblies 405 of keyboard matrix 199) communicated from the current application 312 that is in focus, a user selection of extended keys for a given application 312 in focus, a map of extended keys from a stored lookup table of different combinations of extended keys associated with different corresponding applications 312, etc. It will be understood that application key information 770 may be different (e.g., may designate different number and/or identity of key assemblies 405 for extension and retraction, may designate different peak depression force levels for different key assemblies 405, etc.) for each different user application 312.

For example, as shown in FIG. 3, multiple different key mappings 306 ₁ to 306 _(N) may be defined for respective different games 1 to N that may be executed as applications 312 by host programmable integrated circuit 105. These key mappings 306 may be provided to the key retraction profile configurator application 310 as map files 770, may be retrieved by the key retraction profile configurator application 310 from system storage 135 or memory 107/115, and/or may be defined or edited by a system user. In FIG. 3, the hatched keys of each key map 306 are designated to be extended and active for accepting user input for the current application in focus, with all remaining keys of the given key map 306 designated to be retracted and non-active for accepting any input from a user. As shown, the key mappings 306 ₁ to 306 _(N) designate a different combination of keys to be retracted and non-active for each different game. It will be understood that similar key mappings may be provided for non-game applications such as word processing software (e.g., in which all keys may be mapped to be extended). In a further embodiment, a user may create their own key map for a particular game or other application 312 which was not designed to be supported by the communications API 314, but which the user nonetheless wishes to play or otherwise execute. In this embodiment, the user-created key map will load and become effective upon application launch, and enable all the user's configured gaming or other application keys to be operable and in extended position, and all other keys not used by the game or other application to be retracted and inoperable.

In one exemplary embodiment, a user application 312 may be designed by its developer with its own application developer key map information (e.g., data) to support the communications API 314 of FIG. 3, e.g., as an application developer key map file that includes a starting state for all of the key assemblies 405 of the keyboard matrix 199, dictating which key assemblies 405 are to be initially extended and which keyboard assemblies 405 are to be initially retracted. In such a further embodiment, upon launch of the user application 312, the user application 312 may write its own key map information (e.g., data) as an application developer key map file via direct communication path 771 (i.e., without involvement of key retraction profile configurator application 310) to the communication API 314 and via USB directly to the keyboard MCU 121 as application key configuration parameters 320. As described further herein, such a direct path may also be employed to enable the capability for the user application 312 to provide real-time control to cause retraction and extension of any retractable key assembly 405 or group of retractable key assemblies 405 while the user application 312 is running on host programmable integrated circuit 105, e.g. to communicate ability (e.g., cool-down) and resource availability information from a computer game 312 to the hardware layer 302 via a custom API 314 that communicates key assembly configuration or application key configuration parameters 320 (e.g., key assembly position and availability) to the keyboard MCU 121.

Table 1 below illustrates an example application key map file 770 (which also represents an example of application developer key map information), in the form of an application control list for a given user application 312 that in this example is a first person shooter computer game. Key map file 770 includes a list of the application control commands supported in the user application 312, along with the default key/button, identification of the default control key/button settings for a mouse or retractable keyboard, and the identification of the make and model retractable keyboard, mouse, game controller (not shown), etc. In one embodiment, all retractable key assemblies not listed and assigned to the EPM retractable keyboard in Table 1 may be retracted when the given user application 312 is in focus. Also, included in application key map file 770 (or application developer key map information) of Table 1 are optional peak depression force values that may be designated (and/or user selected) for individual key assemblies 405 for use with a given application 312. As shown in Table 1, in one embodiment values of peak depression force may range from 55 grams to 70 grams. However other peak depression force values are possible, e.g., in one embodiment, values of peak depression force may range from about 40 grams to about 100 grams, although values less than 40 grams and greater than 100 grams are alternatively possible.

TABLE 1 Peak Depres- sion Device Device Key/ Force, Type name Command Button grams Keyboard EPM Retract- Forward W 55 able KB Keyboard EPM Retract- Back S 55 able KB Keyboard EPM Retract- Left A 55 able KB Keyboard EPM Retract- Right D 55 able KB Keyboard EPM Retract- Sprint Left 60 able KB Shift Keyboard EPM Retract- Go prone CTRL 60 able KB Key Keyboard EPM Retract- Crouch C 60 able KB Keyboard EPM Retract- Jump Space 60 able KB bar Keyboard EPM Retract- Use F 65 able KB Equipment Keyboard EPM Retract- Reload R 65 able KB Weapon Mouse Mouse 1 Switch Wheel Up 65 Weapons Mouse Mouse 1 Shoot Left Mouse 55 Button Middle Mouse 65 Mouse Mouse 1 Zoom Button Mouse Mouse 1 Aim Down Right Mouse 65 Sight Button Keyboard EPM Retract- Melee E 60 able KB Keyboard EPM Retract- Night N 65 able KB vision Keyboard EPM Retract- Throw Frag G 60 able KB Grenade Throw Smoke, 60 Flash Keyboard EPM Retract- bang Q able KB Grenades Keyboard EPM Retract- Next 1 65 able KB Weapon Keyboard EPM Retract- Previous 2 65 able KB Weapon Grenade 60 Keyboard EPM Retract- Launcher/ 5 able KB Inventory Keyboard EPM Retract- Air 6 65 able KB Support Keyboard EPM Retract- Menu Esc Key 70 able KB Keyboard EPM Retract- Multiplayer T 70 able KB Text Chat Multiplayer 70 Team Keyboard EPM Retract- Chat Y able KB Multiplayer 70 Voice Keyboard EPM Retract- Chat Z able KB Keyboard EPM Retract- Multiplayer F1 70 able KB Vote Yes Keyboard EPM Retract- Multiplayer F2 70 able KB Vote No Keyboard EPM Retract- Multiplayer F4 70 able KB Scores Keyboard EPM Retract- Take a F12 70 able KB Screenshot

As further shown in FIG. 3, middleware layer 352 may include a communication API 314 to facilitate communication between key retraction profile configurator application 310 and keyboard MCU 121 through OS layer 354. In this regard, profile configurator application 310 may provide user configurable key map information 311 (e.g., as a user configurable application key map file) to communication API 314 before this information is in turn passed to keyboard MCU 121 as application key configuration parameters 320. In one embodiment, application key configuration parameters 320 may reside (be stored) in volatile and/or non-volatile random access memory (RAM) inside keyboard MCU 121, or may alternatively reside in volatile or non-volatile memory separate from keyboard MCU 121 as illustrated in FIG. 3. In any case, keyboard MCU 121 may then access and use the user-configurable key map information within the application key configuration parameters 320 as the basis for controlling retraction and/or peak depression force of individual retractable key assemblies 405 of keyboard matrix 199. Keyboard MCU 121 may be, for example, an ARM Cortex M3 type microcontroller or any other one or more types of programmable integrated circuits suitable for processing digital output signals 732 from key assemblies 405 and controlling extension and retraction of key assemblies 405 in a manner as described herein.

In one embodiment, application key configuration parameters 320 may include a translation of the user configurable key map file information 311 into a format that is understood by EPM decode and drivers 195. In this regard EPM decode and drivers 195 may organize and address the EPMs 197 into (or as) a matrix of rows and columns, and may also ensure that the keycaps 404 of the key assemblies 405 (e.g., corresponding to gaming keys) identified by the output of the game profile configurator application 311 are driven into extended position, and all other key assembly keycaps 404 are driven into retracted position, thus providing magnetic polarity control for each respective EPM 197 of the key assemblies 405 of keyboard matrix 199. In a further embodiment, application key configuration parameters 320 may also be used to block the scan codes 736 from the retracted keys 211 from being reported to the OS 354 via keyboard device drivers 316.

It will be understood that while user configurable key map information 311 may be configurable by a user, it is not necessary that a user actually configure the user configurable key map information 311 before it is passed to keyboard MCU 121 (e.g., user configurable key map information 311 may be the same as application key information 770 originally provided from a user application 312). Moreover, in another embodiment no user configurability is required, and application key information 770 may be passed by key retraction profile configurator application 310 without user modification from application layer 350 to keyboard MCU 121.

Still referring to FIG. 3, keyboard MCU 121 may be coupled as shown to provide addressed key assembly control signals 734 to EPM decode and driver circuitry 195, which in this embodiment are configured to provide a current pulse of either a positive or negative polarity to corresponding individually-addressed EPMs 197 to impart mechanical retraction force 451 to only those key assemblies 405 of keyboard matrix 199 that are designated to be retracted by the current instance of the user-configurable key map information within the application key configuration parameters 320 of keyboard MCU 121 so as to match the current user application 312 that is in focus. Keyboard MCU 121 may also provide addressed key assembly control signals 734 to EPM decode and driver circuitry 195, to provide a current pulse of either a positive or negative polarity to corresponding individually-addressed EPMs 197 of respective key assemblies 405 to impart each identified key assembly 405 of keyboard matrix 199 into an extended (active) position. Alternatively or additionally, keyboard MCU 121 may provide addressed key assembly control signals 734 to cause EPM decode and driver circuitry 195 to provide an appropriate current pulse to corresponding individually-addressed EPMs 197 to impart a desired peak depression force to only those key assemblies 405 of keyboard matrix 199 that are designated by the current instance of the user-configurable key map information within the application key configuration parameters 320 of keyboard MCU 121 so as to match the current user application 312 that is in focus.

As further shown, keyboard MCU 121 may also be coupled to receive digital output signals 732 from individual user-depressed active extended keys 210 of keyboard matrix 199, while ignoring any input signals received from individual retracted keys 211 of keyboard matrix 199, which are treated by MCU 121 as being inactive. Keyboard MCU 121 may be coupled to in turn provide appropriate scan codes 736 to keyboard driver 316 of OS layer 354 (e.g., such as PS2 Windows keyboard driver as shown or other suitable keyboard driver logic) that correspond to the current user-depressed (and active) keys 210. Keyboard driver 316 may then provide user keyboard events 760 corresponding to the scan codes 736 of the currently depressed extended (and active) key/s 210 to the user application 312 that is currently in focus. It will be understood that the embodiment of FIG. 3 is exemplary only, and that in other embodiments a programmable integrated circuit (e.g., such as auxiliary EC 111) separate from keyboard controller 121 may be employed to receive application key configuration parameters 320 and to provide addressed key assembly control signals 734 to EPM decode and driver circuitry 195. It also not necessary that retracted keys 211 be made inactive when retracted.

In a further embodiment, a direct path may be employed to enable the capability for a user application 312 to provide real-time control to cause retraction and extension of any retractable key assembly 405 or group of retractable key assemblies 405 while the user application 312 is running on host programmable integrated circuit 105. For example, as described in relation to FIGS. 2B-2C herein, the user application 312 may be a first person shooter (FPS) game. Upon its launch, the FPS game 312 may send key map information over direct communication path 771 to the communication API 314 and via USB as application key configuration parameters 320 to the keyboard MCU 121 that identifies a group (e.g., two dozen or other selected number) of key assemblies 405 that are to be used by the game 312. One example of an API 314 that may be employed for accepting and communicating such real time key assembly control to keyboard MCU 121 may be found described in U.S. Pat. No. 7,772,987, which is incorporated herein by reference in its entirety. Keyboard MCU 121 may respond by providing key assembly control signals 734 to EPM decode and driver circuitry 195 to cause the identified key assemblies 405 from the received key map information to be placed in the extended position 210 and made operational, while all other key assemblies 405 not identified as being used by the game are placed in the retracted position 211 and made non-operational.

Later, once the user starts playing the game 312, the game 312 may provide real time updated key map information by direct communication path 771 to API 314 and via USB as updated application key configuration parameters 320 to retract or extend a single key in response to in-game events as they occur (e.g., retracting the “G” key assembly when the user runs out of grenades, extending the “G” key assembly once the user has a replenished supply of grenades). In one embodiment, the updated key map information (e.g., updated application key configuration parameters 320) may only list a single key assembly 405 or a subset of the keyboard matrix key assemblies 405 which currently require a real time change in position (i.e., from retracted position 211 to extended position 210 or vice versa). As a result, the updated key map information list will typically be smaller than application developer key map file used at application launch, and will therefore execute significantly faster (e.g., helping to ensure low latency operation) and to ensure the real-time retraction/extension operation appears to be very responsive.

In one embodiment, the direct path from the application 312 to the keyboard MCU 121 allows for minimal latency to ensure responsive key extension/retraction after receiving the event command generated by the game. For example, the game 312 may provide real time updated key map information via direct communication path 771 to API 314 and via USB as updated application key configuration parameters 320 to keyboard MCU 121 to retract a given key during a “cool down” period after a weapon is fired during which the weapon is unusable, e.g., a game 312 may provide real time updated key map information via a direct communication path through API 314 and USB as updated application key configuration parameters 320 to keyboard MCU 121 to first instruct the cannon key (e.g., key assembly Q of FIGS. 2B-2D) via a direct communication path through API 314 to retract and be non-operational, and then to extend and to become operational again upon completion of the cool down period.

FIGS. 4A-4D illustrate a single retractable key assembly 405 of keyboard matrix 199 as it may be implemented according to one exemplary embodiment for each of the multiple key assemblies 405 of a keyboard matrix 199. In this embodiment two separate “on-off” EPMs 197 are employed to selectively extend and retract the keycap 404 of the assembly, e.g., in one embodiment with 2 millimeter of keycap travel between extended position 210 and retracted position 211 although keycap travel values of greater or less than 2 millimeters are also possible. Such an on-off EPM 197 may be selectively turned “ON” by a current pulse 450 to produce an attractive magnetic force, and turned “OFF” by another current pulse so that it does not produce an attractive magnetic force. In a further embodiment described herein, at least EPM 197 b may be controlled to produce different magnitudes of attractive magnetic force by varying the amplitude of a current pulse 450 that is applied to turn “ON” the EPM 197 (e.g., by using pulse width modulated signal to control current amplitude or other suitable current control technique and/or circuitry) so as to vary the degree of magnetization, which in turn varies the upward bias applied to keycap 404 and the resulting required peak depression force for the key switch mechanical structure 403 of key assembly 405, i.e., to translate into different typing forces exhibited by the same key assembly 405.

In one embodiment illustrated in the inset of FIG. 4A, each of EPM's 197 may include two permanent magnet material components (permanent magnets) with very different intrinsic coercivities (e.g., such as relatively low coercivity AlNiCo and relatively high coercivity permanent neodymium (NdFeB) magnetic materials), placed side by side with their polarities in parallel direction. In such an embodiment, a magnetically permeable material (such as Iron) may be placed as a shunt on the ends of the magnetic materials, completely covering the ends of both magnetic materials. Also in this embodiment, a conductive wire (e.g., copper or other suitable conductive wire) is wrapped in a coil around both magnetic materials, e.g., covering the entire length of the magnetic materials per the exemplary illustration of FIG. 4A. This configuration may be advantageous, for example, for use with relative small scale applications. However, in alternative embodiments a conductive wire may be wrapped in a coil around only one of the magnetic materials, such as the AlNiCo. In the illustrated embodiment, the coercivity values of the two magnetic materials may be selected to be so different so as to allow use of the coil to easily generate a magnetic field that is stronger than the intrinsic coercivity and fully saturated values of a first one of the magnetic materials (e.g., Alnico magnetic material), but that is less than the intrinsic coercivity value of the second one of the magnetic materials (e.g., NdFeB magnetic material). So in such an embodiment, the current pulse will re-magnetize the first magnetic material (e.g., Alnico) without affecting the second magnetic material (e.g., NdFeB).

Thus, in one embodiment, the relatively low intrinsic coercivity first magnetic material (e.g., semi-hard_AlNiCo) material may be magnetized and demagnetized by different polarity current pulses 450 passed through the conductor coil. In this regard, a current pulse 450 passed through the coil around the magnetically soft AlNiCo material can re-magnetize that material in a desired direction, and the current pulse 450 only has to be present long enough to generate a magnetic field substantially strong enough to re-magnetize the AlNiCo material in the desired direction. When the current pulse 450 is switched off, the AlNiCo will hold that polarization until another strong field is presented. When both the AlNiCo and NdFeB are magnetically polarized in the same direction, the magnetic fields exit the iron shunts to interact with the external world. When the AlNiCo and NdFeB magnets are polarized in opposite directions, the fields loop between the two magnets entirely inside the iron shunts to cancel themselves out, essentially turning off the magnet to the outside world. The amount of magnetic field exiting the iron shunts (field strength) may also be controlled by varying the amplitude of the current pulse 450.

In one embodiment, the amplitude of a current pulse 450 may be controlled to be small enough that the magnetic field it generates is greater than the relatively lower intrinsic coercivity magnetic material (e.g., AlNiCo) but at the same time less than the relatively higher intrinsic coercivity value of the second magnetic material (e.g., NdFeB) of an EPM 197. In this regard, once steady state current flow through the coil is achieved, the magnetic field generated by the coil is proportional to the number of turns in the coil and the amplitude of the current. Given that the coil has a fixed number of turns (windings) and therefore a fixed resistance, voltage applied to the coil may be varied to control the resulting current 450 through the coil of an EPM 197.

In FIGS. 4A-4D, a retractable key assembly 405 of this embodiment has a key switch mechanical structure 403 that includes a movable keycap component 404 (e.g., plastic or other suitable material) that is supported above a base component (e.g., a keyboard base plate 402 such as planar sheet metal, plastic, etc.), by two opposing angled support arms (e.g., lever arms or scissor components) 406 and 408. In one embodiment, keyboard base plate 402 may be a common planar base plate that extends beneath a plurality of retractable key assemblies 405 of keyboard matrix 199, and may contain, support and/or be positioned above circuitry such as keyboard or peripheral device circuitry (e.g., key press detection or key signal output circuitry configured to output a key output signal for each depressed key assembly 405, lighting circuitry, etc.). For example a key press detection membrane 407 may be positioned on top of a metal base plate 402 and aligned with a rigid pin 409 downwardly projecting from underside of keycap 404 (shown in dashed outline in FIGS. 4A and 4B) such that an output key signal 732 unique to the given key assembly 405 is produced at a key signal output when pin 409 contacts and compresses key press detection membrane as illustrated in FIG. 4B. Optional keyboard lighting may also be provided from a lighting element (e.g., LED or light pipe) positioned below keyboard base plate 402 to direct light upward toward keyboard base plate 402. One or more aligned openings may be provided within keyboard base plate 402 and membrane 407 beneath keycap 404 to allow the light to shine on the underside of keycap 404 and through optional light transmission features (e.g., opening/s or translucent features) provided within keycap 404 to be observed by a user positioned above the keycap 404. Further information on example keyboard matrix structure and circuitry may be found in U.S. Pat. Nos. 8,674,941; 9,246,487; 8,748,767; and 9,368,300; each of the foregoing being incorporated herein by reference in its entirety for all purposes.

The retractable key assembly 405 of this embodiment is shown with keycap 404 in extended position 210 in the cross-section view of FIG. 4A, and is shown with keycap 404 in retracted position 211 in the cross-section view of FIG. 4B. As further shown in FIGS. 4A-4D, movable angled support arm components 406 and 408 are coupled to pivot relative to base plate 402 about respective pivot points or fulcrums, e.g., in this case provided in the form of pivot pins 491 and 493 that extend outwardly from opposing sides of support arms 406 and 408 and that are received by corresponding support rails 419 that extend upward from base plate 402. First and proximal ends 406 a and 408 a of respective angled support arms 406 and 408 each include opposing pins 411 or 413 that are slidably received in respective channels 410 and 412 defined in corresponding opposing sides of keycap 404 as shown. In this configuration, keycap 404 is retractable from an extended position 210 of FIG. 4A to retracted condition 211 of FIG. 4B by virtue of downward pivot of first ends 406 a and 408 a of respective angled support arms 406 and 408 about pins 491 and 493, and by simultaneous outward sliding of opposing pins 411 within channels 410 and 412, as shown in FIG. 4B. As further shown, a sliding coupler 465 may be provided to couple second ends 406 b and 408 b of respective angled support arms 406 and 408 together in movable relationship to help ensure horizontally-even upward and downward displacement of keycap 404.

Also shown in FIGS. 4A-4D is movable angled magnetically permeable (e.g., ferromagnetic) body component (e.g., ferromagnetic lever or rocker plate 420) that has a first end 420 a that is coupled to or otherwise integrated with first angled support arm 406 to mechanically secure or tie together first end 420 a of angled magnetically permeable body 420 and first angled support arm 406 together in fixed relationship so that they move together, e.g., in this embodiment a first end 420 a of angled magnetically permeable plate 420 is received (e.g., inserted into or surrounded by molded support arm 406) within a corresponding recess 423 defined in support arm 406 as shown. However, one or more magnetically permeable plates may be otherwise secured or integrated with an angled support arm in any other manner suitable for implementing the key retraction capability described further herein. In one embodiment, angled support arms 406 and 408 may be constructed of non-magnetically permeable material (e.g., non-magnetically permeable plastic) so as to not to interact with magnetic field of EPMs 197 and/or their effect on angled magnetically permeable plate 420 during operation.

Examples of ferromagnetic materials that may be employed as magnetically permeable materials in the embodiments herein (e.g., as shunts, plate, levers, etc.) include, but are not limited to, iron, nickel, cobalt, or alloys including some amount of one or more of those elements. For example, in one exemplary embodiment, a magnetically permeable lever or plate 420 may be composed of a ferromagnetic alloy having high magnetic permeability, e.g., such as 400 series stainless steels, or “electrical-steel” or “silicon-steel” having relative high magnetic permeability and relatively low coercivity. Examples of permanent magnet materials that may be employed in the embodiments herein (e.g., for components of EPMs 197, attached to angled support arms, etc.) include, but are not limited to Neodymium (Nd), Samarium Cobalt, Alnico, Ceramic, etc.

As shown in FIG. 4A, at least two EPMs 197 may be provided on, within or beneath baseplate 402, e.g., with a first EPM 197 a being at least partially aligned with and beneath (or otherwise positioned to emit an external magnetic field that acts on) the first end 420 a of angled magnetically permeable plate 420 and a second EPM 197 b being at least partially aligned with and beneath the (or otherwise positioned to emit an external magnetic field that acts on) second end 420 b of angled magnetically permeable plate 420. EPMs 197 may be mounted beneath a solid base plate 402 (where baseplate 402 is non-magnetically permeable material such as plastic), or may be mounted within or beneath corresponding aligned openings defined within baseplate 402 (where baseplate 402 is magnetically permeable material such as steel or is non-magnetically permeable material such as plastic). A current pulse 450 b of appropriate polarity may be provided to EPM 197 b to turn ON the external magnetic field 489 b of EPM 197 b while at the same time a current pulse 450 a of appropriate polarity may be provided to EPM 197 a to turn OFF the external magnetic field 489 a of EPM 197 a, and vice-versa. In this embodiment, EPMs 197 a and 197 b are positioned to selectably emit an upward external magnetic field that is at least partially aligned with (or acts on) first end 420 a and second end 420 b of angled magnetically permeable plate 420, respectively. EPMs 197 a and 197 b are also positioned to selectably emit an upward external magnetic field that is not aligned with (or does not act on) second end 420 b and first end 420 a of angled magnetically permeable plate 420, respectively. Thus, external magnetic fields of EPMs 197 a and 197 b may be controlled so that an upward external magnetic field is applied to and acts on only one end 420 a or 420 b of magnetically permeable plate 420 at a time.

To extend the keycap 404 of FIG. 4A upward, the external magnetic field of EPM 197 b may be placed in the ON condition and the external magnetic field of EPM 197 a may at the same time be placed in the OFF condition to attract the second end 420 b of angled magnetically permeable plate 420 downward toward baseplate 402. When the second end 420 b of angled magnetically permeable plate 420 is attracted downward toward baseplate 402 it causes the first end 420 a of angled magnetically permeable plate 420 to separate and move upwards and away from baseplate 402 together with coupled first end 406 a of first angled support arm 406. Keycap 402 is in turn moved upwards by upward movement of first end 406 a of support arm 406 while its corresponding pin 411 slides inward within channel 410. This upward movement of keycap 404 is mechanically transmitted through keycap 404 to cause simultaneous upward movement of second end 408 a of second angled support arm 408 while its corresponding pin 411 slides inward within channel 412 as shown. In the extended position 210 of FIG. 4A, the amount of applied upward bias force that resists downward depression of key assembly 405 by a user (and that returns key assembly 405 upward after it has been depressed by a user) is provided by virtue of the amount of downward attractive force applied to second end 420 b of angled magnetically permeable plate 420 by EPM 197 b in its ON condition.

Thus it is optionally possible in one embodiment to vary the peak depression force required by a user to depress the extended key assembly 405 by varying the amplitude of the current pulse 405 applied to turn “ON” EPM 197 b, e.g., current pulses 450 may be applied to EPM 197 b that are of different selectable amplitudes greater than minimally required to extend key assembly 405 so as to result in different selectable magnitudes of external attractive magnetic force emitted from EPM 197 b that attracts the second end 420 b of angled magnetically permeable plate 420 downward toward baseplate 402 so as to vary the peak depression force required by a user to overcome the magnetic force emitted from EPM 197 b and depress the extended key assembly to cause output of key signal from key assembly 405.

Referring to FIG. 4B, keycap 404 may be retracted by placing the external magnetic field of EPM 197 a in the ON condition (e.g., by applying current pulse 450 a of opposite polarity) to attract the first end 420 a of angled magnetically permeable plate 420 downward toward baseplate 402 at the same time that the external magnetic field of EPM 197 b is placed in the OFF condition (e.g., by applying current pulse 450 b of opposite polarity). When the first end 420 a of angled magnetically permeable plate 420 is attracted by EPM 197 a it moves downwards toward baseplate 402 together with coupled first end 406 a of first angled support arm 406 as shown in FIG. 4B. This in turn causes keycap 402 to move downwards together with first end 406 a of angled support arm 406 while its corresponding pin 411 slides outward within channel 410. This downward movement of keycap 404 is mechanically transmitted through keycap 404 to cause simultaneous downward movement of second end 408 a of second angled support arm 408 while its corresponding pin 411 slides outward within channel 412 as shown.

As further shown in FIGS. 4A-4B it is optionally possible to include one or more additional EPMs 197 x that are positioned adjacent EPM 197 b and also at least partially aligned with (or otherwise positioned to emit an external magnetic field that acts on) and beneath the second end 420 b of angled magnetically permeable plate 420. as shown. In this embodiment, each additional EPM 197 x may be optionally and selectably turned “ON” by a separate current pulse 450 x at the same time that EPM 197 b is turned “ON” by current pulse 450 b, i.e., to selectably and optionally provide an increased magnitude of external attractive magnetic force emitted from a combination of EPMs 197 b and 197 x to attract the second end 420 b of angled magnetically permeable plate 420 downward toward baseplate 402 with greater force than when only EPM 197 b is turned “ON” by current pulse 450 b. In this way the peak depression force required by a user to overcome the magnetic force emitted from EPM 197 b may be increased when desired by turning “ON” both EPMs 197 b and 197 x (while EPM 197 a is “OFF”), and may be decreased again by turning “ON” EPM 197 b with EPM 197 a “OFF” and with all or a portion of additional EPMs 197 x turned “OFF”.

FIGS. 5A-5D illustrate a single retractable key assembly 405 of keyboard matrix 199 as it may be configured according to another exemplary embodiment of the disclosed systems and methods, and as it may be implemented for each of the multiple keycaps 404 of a keyboard matrix 199. In this embodiment, keycap 404 is in extended position 210 in the cross-section view of FIG. 5A, and is shown with keycap 404 in retracted position 211 in the cross-section view of FIG. 5B. As further shown in FIGS. 5A-5D, angled support arms 406 and 408 of key switch mechanical structure 403, as well as base plate 402, are provided to operate in a manner similar to that described in relation to FIGS. 4A-4D. Also, in the embodiment of FIGS. 5A-5D, a first end 420 a of angled magnetically permeable plate 420 a is coupled to or otherwise integrated with first angled support arm 406 to secure these components 420 and 406 together in movable relationship in similar manner as described in relation to FIGS. 4A-4D.

As shown in FIGS. 5A-5D, a single “on-off” EPM 197 may be provided on, within or beneath baseplate 402 and at least partially aligned with and beneath (or otherwise positioned to emit an external magnetic field that acts on) the second end 420 b of angled magnetically permeable plate 420 with no EPM 197 aligned with (or positioned to emit an external magnetic field that acts on) the first end 420 a of angled magnetically permeable plate 420. EPM 197 of FIGS. 5A-5D may be mounted relative to base plate 402 as previously described in relation to FIGS. 4A-4D. In the embodiment of FIGS. 5A-5D, a current pulse 450 of appropriate polarity may be provided to EPM 197 to turn ON an attractive external magnetic field 489 of EPM 197 that is at least partially aligned with (or otherwise positioned to emit an external magnetic field that acts on) and attracts first end of 420 a of angled magnetically permeable plate 420, and of a current pulse 450 of opposite polarity may be provided to turn OFF the attractive external magnetic field 489 of EPM 197 so as to not attract first end of 420 a of angled magnetically permeable plate 420. As further shown in FIGS. 5A-5D, at least one resilient material component in the form of a semi-elliptical or leaf spring 530 (e.g., steel wire spring, plastic spring, etc.) is provided that is fixedly coupled relative to base plate 402, e.g., coupled to at least one of rails 419 at its center by connector 421 or otherwise coupled directly or indirectly to base plate 402. In the embodiment of FIGS. 5A-5D, opposing ends of spring 530 are positioned to contact and rest on bosses 501 and 503 that extend outwardly from the opposite sides of angled support arms 406 and 408, respectively. Other types of springs that may be alternately employed for the same purpose include tension coil spring/s, torsion spring/s, etc.

As shown in FIGS. 5C and 5D, a separate spring 530 may be provided at each of opposing sides of angled support arms 406 and 408, and a corresponding pair of bosses 501 and 503 may be provided to extend from each of opposing sides of angled support arms 406 and 408. In such an embodiment, the separate springs 530 may be configured to operate in tandem on opposing sides of the retractable key assembly. Each spring 530 may be positioned and tensioned between a connector 421 and corresponding bosses 501 and 503 so as to bias keycap 404 in downward direction toward retracted position 211 to maintain keycap 404 in a retracted position 210 in the absence of an applied attractive external magnetic field of EPM 197 (i.e., when attractive external magnetic field of EPM 197 is turned OFF) as shown in FIG. 5B. EPM 197 may be configured to produce an attractive external magnetic field of sufficient strength to attract the second end 420 b of angled magnetically permeable plate 420 downward toward baseplate 402 and raise the first end of 420 a of angled magnetically permeable plate 420 with sufficient force to overcome the downward bias of spring 530 as illustrated in FIG. 5A. Thus, to extend the keycap 404 of FIG. 5A upward to extended position 210, the external magnetic field of EPM 197 may be placed in the ON condition to attract the second end 420 b of angled magnetically permeable plate 420 downward toward baseplate 402 to cause the first end 420 a of angled magnetically permeable plate 420 to separate and move upwards and away from baseplate 402 together with coupled first end 406 a of first angled support arm 406. Keycap 404 may be retracted by placing the external magnetic field of EPM 197 in the OFF condition to release the second end 420 b of angled magnetically permeable plate 420 to allow spring 530 to move keycap 404 in downward direction toward retracted position 211.

Although the key switch mechanical structure 403 embodiment of FIGS. 5A-5D employs a leaf spring 530, it will be understood that any other suitable type of one or more springs (e.g., tension coil spring/s, torsion spring/s, etc.) may be provided and configured to bias a keycap 404 in downward direction toward retracted position 211. In an alternate embodiment, one more springs may be provided to bias a keycap 404 in an upward direction toward an extended position 210. In such an alternate embodiment, a single EPM 197 may be positioned be provided on, within or beneath baseplate 402 and aligned with (or otherwise positioned to emit an external magnetic field that acts on) the first end 420 a of angled magnetically permeable plate 420 with no EPM 197 aligned with (or positioned to emit an external magnetic field that acts on) the second end 420 a of angled magnetically permeable plate 420 such that a current pulse 450 of appropriate polarity may be provided to EPM 197 to turn ON an attractive external magnetic field of EPM 197 to attract first end 420 a of angled magnetically permeable plate 420 downward so as to retract keycap 404 in a downward direction toward a retracted position 211, and a current pulse 450 of opposite polarity may be provided to turn OFF the attractive external magnetic field of EPM 197 so as to move bias keycap 404 in an upward direction toward extended position 211.

In the embodiment of FIGS. 5A-5D, it is optionally possible in one embodiment to vary the peak depression force required by a user to depress the extended key assembly 405 by varying the amplitude of the current pulse 405 applied to turn “ON” EPM 197, e.g., current pulses 450 may be applied to EPM 197 that are of different selectable amplitudes greater than minimally required to extend key assembly 405 against the downward bias of spring 530 so as to vary the peak depression force required by a user touch together with downward bias of spring 530 to overcome the magnetic force emitted from EPM 197 to depress the extended key assembly to cause output of a key signal from key assembly 405.

As further shown in FIGS. 5A-5B it is optionally possible to include one or more additional EPMs 197 x that are positioned adjacent EPM 197 and also at least partially aligned with and beneath (or otherwise positioned to emit an external magnetic field that acts on) the second end 420 b of angled magnetically permeable plate 420 as shown. In this embodiment each EPM 197 x may be optionally and selectably turned “ON” by a separate current pulse 450 x at the same time that EPM 197 is turned “ON” by current pulse 450, i.e., to selectably and optionally provide an increased magnitude of external attractive magnetic force emitted from a combination of EPMs 197 and 197 x to attract the second end 420 b of angled magnetically permeable plate 420 downward toward baseplate 402 with greater force than when only EPM 197 is turned “ON” by current pulse 450. In this way the peak depression force required by a user together with downward bias of spring 530 to overcome the magnetic force emitted from EPM 197 may be increased when desired by turning “ON” both EPMs 197 and 197 x, and may be decreased again by turning “ON” EPM 197 with all or a portion of additional EPMs 197 x turned “OFF”.

FIGS. 6A-6D illustrate a single retractable key assembly 405 of keyboard matrix 199 as it may be configured according to another exemplary embodiment of the disclosed systems and methods, and as it may be implemented for each of the multiple keycaps 404 of a keyboard matrix 199. In this embodiment, keycap 404 is in extended position 210 in the cross-section view of FIG. 6A, and is shown with keycap 404 in retracted position 211 in the cross-section view of FIG. 6B. As further shown in FIGS. 6A-6D, key switch mechanical structure 403 has angled support arms 406 and 408, as well as base plate 402, that are provided to operate in a manner similar to that described in relation to FIGS. 4A-4D. In this embodiment, at least one permanent magnet 610 may be provided in or on a second end 406 b of angled support arm 406 as shown (e.g., as a bar-shaped magnet, or other suitable shape having two magnetic poles oriented as shown). In this embodiment, permanent magnet material of permanent magnet 610 may be any permanent magnet material having a magnetization, or magnetic field strength and polarity, that is not affected by current pulses 450. Examples of suitable permanent magnet materials for use as permanent magnet 610 include, but are not limited to, Neodymium grade N35, N40, N42, N45, N52, etc. magnetic materials.

As shown in FIGS. 6A-6D, a single reversible polarity or polarity-switching EPM 197 may be provided on, within or beneath baseplate 402 and at least partially aligned with and beneath (or otherwise positioned to emit an external magnetic field that acts on) the second end 406 b of angled support arm 406 with no EPM 197 aligned with (or positioned to emit an external magnetic field that acts on) the first end 406 a of angled support arm 406. In one embodiment illustrated in the insets of FIGS. 6A and 6B, each of polarity switching EPM's 197 of FIG. 6A may include a single permanent magnet or magnetic material component (e.g., AlNiCo or other suitable magnetic material such as Neodymium, etc.), with a conductive wire (e.g., copper or other suitable conductive wire) wrapped in a coil around the permanent magnet material, e.g., covering the entire length of the magnetic material. For example, It will be understood that a magnetic material may be selected based on its intrinsic coercivity, e.g., Alnico magnetic material has a relatively lower intrinsic coercivity so that it is requires current pulse of lower amplitude/voltage to remagnetize (or flip or switch polarity) than other permanent magnet materials such as Neodymium.

In one embodiment a linear permanent magnet or other shape magnet having two magnetic poles and having no attached shunts may be provided for a polarity-switching EPM 197 as illustrated in the inset of FIG. 6A. For example, as illustrated in insets of FIGS. 6A and 6B, orientation of the EPM permanent magnet axis extending between its poles may be vertical, so that a first one of its switchable magnetic poles faces upward toward overlying permanent magnet 610 and so that the second and opposite one of its switchable-polarity magnetic poles faces downward. In such a case, permanent magnet 610 may be oriented so that one of its fixed polarity poles (e.g., positive pole in FIGS. 6A and 6B) faces downward toward the switchable upper pole of EPM 197, and such that the that the other one of its poles (e.g., negative pole in FIGS. 6A and 6B) faces upward and away from underlying EPM 197. Thus, in a first attracting polarity state (e.g., P1) of EPM 197, switchable upper pole of EPM 197 may be controlled to have a magnetic polarity that is opposite to (e.g., negative in FIGS. 6A and 6B) the magnetic polarity of the overlying pole of permanent magnet 610 and interacts with (or acts on) the magnetic polarity of the overlying pole of permanent magnet 610. On the other hand, in a second repelling polarity state (e.g., P2) of EPM 197, switchable upper pole of EPM 197 may be controlled to have a magnetic polarity that is the same as (e.g., positive in FIGS. 6A and 6B) the magnetic polarity of the overlying pole of permanent magnet 610 and interacts with (or acts on) the magnetic polarity of the field of overlying pole of permanent magnet 610.

In an alternative embodiment, magnetically permeable material (such as Iron or Fe) may optionally be coupled as a shunt on each ends of the permanent magnet material to steer the magnetic flux, e.g., at a right angle to the axis of the EPM permanent magnet (e.g., in a manner similar to a horse-shoe shaped magnet). For example, linear orientation of the EPM permanent magnet axis (extending between its opposite magnetic poles) may be horizontal, with a vertically upward pointing magnetically permeable shunt segment provided on each end. In such a case, the axis between the poles of permanent magnet 610 may be oriented horizontally and parallel to the magnetic axis of EPM permanent magnet, such that the positive pole at one end of the permanent magnet 610 is at least partially aligned with (or otherwise positioned to be acted on by an external magnetic field emitted by) one of the upward-extending EPM magnet shunts, and such that the negative pole of the permanent magnet 610 is at least partially aligned with (or otherwise positioned to be acted on by an external magnetic field emitted by) the other and opposite one of the upwardly-extending EPM magnet shunts. Thus, in a first attracting polarity state (e.g., P1) of EPM 197, each of the upward extending shunts has a magnetic polarity that is opposite to the magnetic polarity of the overlying pole of permanent magnet 610 with which it interacts. On the other hand, in a second repelling polarity state (e.g., P2) of EPM 197, each of the upward extending shunts now has a magnetic polarity that is the same as the magnetic polarity of the overlying pole of permanent magnet 610 with which it interacts.

EPM 197 of FIGS. 6A-6D may be mounted relative to base plate 402 as previously described for other EPMs described in relation to FIGS. 4A-4D. In the embodiment of FIGS. 6A-6D, a first current pulse 450 of appropriate polarity may be provided to polarity-switching EPM 197 to cause the permanent magnet of EPM 197 to produce an attractive external magnetic field 689 of a first polarity “P1” that is at least partially aligned with and attracts the permanent magnet 610 of second end 406 b of angled support arm 406 to cause second end 406 b of angled support arm 406 to move downward toward base plate 402 and first end 406 a of angled support arm 406 to move upward and away from base plate 402 to extend keycap 404 of key switch mechanical structure 403 into extended position 210 as shown in FIG. 6A. A second current pulse 450 of opposite polarity may be provided to cause the permanent magnet of EPM 197 to produce a repellant external magnetic field 691 of a second and opposite polarity “P2” that is at least partially aligned with and repels the permanent magnet 610 of second end 406 b of angled support arm 406 to cause second end 406 b of angled support arm 406 to move upward and away from base plate 402 and first end 406 a of angled support arm 406 to move downward and toward base plate 402 to retract keycap 404 into retracted position 210 as shown in FIG. 6B. The embodiment of FIGS. 6A-6D may be implemented in a manner that saves power over some other embodiments. It will be understood that identity of attractive and repellant fields of EPM 197 are determined relative to the magnetic field orientation of permanent magnet 610.

In the embodiment of FIGS. 6A-6D, it is optionally possible in one embodiment to vary the peak depression force required by a user to depress the extended key assembly 405 by varying the amplitude of the current pulse 405 applied to cause EPM 197 to produce an attractive external magnetic field of a first polarity “P1”, e.g., current pulses 450 may be applied to EPM 197 that are of different selectable amplitudes greater than minimally required to attract permanent magnet 610 of second end 406 b of angled support arm 406 so as to vary the peak depression force required by a user touch to overcome this attractive magnetic force emitted from EPM 197 to depress the extended key assembly to cause output of a key signal from key assembly 405.

As further shown in FIGS. 6A-6B it is optionally possible to include one or more additional EPMs 197 x that are each positioned adjacent EPM 197 and also at least partially aligned with and beneath (or otherwise positioned to emit an external magnetic field that acts on) the at least one permanent magnet 610 in or on a second end 406 b of angled support arm 406. In this embodiment each additional EPM 197 x may be optionally and selectably controlled by a separate current pulse 450 x to produce an attractive external magnetic field of a first polarity “P1” that attracts the permanent magnet 610 of second end 406 b of angled support arm 406 at the same time that EPM 197 is also controlled to produce the attractive external magnetic field of first polarity “P1” by a separate current pulse 450 i.e., to selectably and optionally provide an increased magnitude of external attractive magnetic force emitted from a combination of EPMs 197 and 197 x to attract the second end 420 b of angled magnetically permeable plate 420 downward toward baseplate 402 with greater force than when only EPM 197 is controlled to produce attractive external magnetic field “P1” by current pulse 450. In this way the peak depression force required by a user to overcome the magnetic force emitted from EPM 197 may be increased when desired by causing one or more additional EPMs 197 x to also emit the attractive external magnetic field “P1”, and may be decreased again by causing EPM 197 to emit the attractive external magnetic field “P1” (e.g., with all or a portion of additional EPMs 197 x emitting the external magnetic field of second polarity “P2” to repel the permanent magnet 610 of second end 406 b of angled support arm 406, and/or by providing a reduced amplitude current pulse 450 x to cause one or more additional EPMs 197 x to emit a reduced external magnetic field of second polarity “P2” to less strongly repel the permanent magnet 610 of second end 406 b of angled support arm 406).

It will be understood that the embodiments described and illustrated in FIGS. 4A to 6D are exemplary only, and that positions of EPMs and magnetically permeable materials (e.g., such as magnetically permeable plates) may be interchanged, e.g., EPMs may be mounted on the movable key assembly components, while aligned magnetically permeable materials may be fixedly mounted to a baseplate, etc. Moreover, other types of retractable key assembly key mechanism configurations are possible that are configured (e.g., employing one or more EPMs, movable key assembly components, and/or spring or other resilient material components that bias the key assembly upward away from the base or baseplate) to selectably retract and extend an individual keycap or individual keycaps of keyboard matrix.

For example one or more EPMs may be fixedly positioned beneath a spring loaded mechanical key switch assembly having a keycap coupled to a shaft, plunger body, internal spring element (e.g., helical spring or compression coil), and plunger axle movably received within a plunger cavity that is mounted on or to a baseplate (e.g., metal plate, printed circuit board, plastic plate, etc.) such as described in U.S. Pat. No. 9,343,248 which is incorporated herein by reference in its entirety for all purposes. In such an alternative embodiment, a magnetically permeable material (e.g., magnetically permeable plate or body) may be fixedly coupled to a movable key assembly component (e.g., plunger body and/or shaft) of the mechanical key switch assembly, and at least one EPM may be fixedly mounted on, within or beneath the baseplate in a position that is at least partially aligned with and beneath (or otherwise positioned emit an external magnetic field that acts on) the magnetically permeable material. In such an alternate embodiment, a current pulse of appropriate first polarity may be provided to the EPM turn ON the external magnetic field of the EPM to attract the magnetically permeable material and movable key assembly components (e.g., keycap, shaft, plunger body, and plunger axle) downward into a retracted position against (and overcoming) an upward force imparted by the compressed internal spring element, while another current pulse of opposite polarity may be provided to the EPM to turn OFF the external magnetic field of the EPM so as to allow the upward force imparted by the compressed internal spring element to re-extend the movable key assembly components of the key assembly upward into extended position.

Other types of key assemblies that may be configured with one or more EPMs to selectably retract and extend movable key assembly components include, but are not limited to, collapsible dual lever (scissor) action key mechanism that supports a keycap over a resilient rubber or other flexible dome structure/member and key signal output circuitry, such as described in U.S. Pat. Nos. 8,748,767 and 8,674,941, each of which is incorporated herein by reference in its entirety for all purposes. Similar to described above, a magnetically permeable material (e.g., magnetically permeable plate or body) may be fixedly coupled to a movable component (e.g., keycap, lever, etc.) of the mechanical key switch assembly, and at least one EPM may be fixedly mounted on, within or beneath the baseplate in a position that is at least partially aligned with and beneath (or otherwise positioned emit an external magnetic field that acts on) the magnetically permeable material such that a first current pulse may be provided to turn ON and the external magnetic field of the EPM to selectably attract the magnetically permeable material and retract the movable components and keycap of the key assembly while overcoming upward force of (and compressing) the resilient rubber dome. A second and opposite polarity current pulse may be provided to turn OFF and the external magnetic field of the EPM to selectably release the magnetically permeable material and allow the resilient rubber dome to upwardly bias the movable components and keycap of the key assembly.

It will also be understood that various features of the disclosed systems and methods may be implemented with types of keys other than a QWERTY or similar style notebook or desktop computer keyboard. In this regard, one or more of the disclosed retractable keys may be similarly implemented for any type of user-input device that employs one or more keys, e.g., such as a computer mouse, game controller, control panel (e.g., for an automobile, aircraft, chemical plant, etc.).

FIG. 7 is a flowchart 700 illustrating interaction between hardware layer 302 and other previously-described layers 350, 352 and 354 of an information handling system 100 according to one exemplary embodiment of the disclosed systems and methods. As shown in FIG. 7, hardware layer 302 is configured to allow a user to provide user-input 196 by depressing individual keycaps of key assemblies 405 and an optional non-EPM driven Mode Toggle Key or button 200 of key matrix 199 to cause production of corresponding digital key output signals 732 at a key signal output to keyboard controller 121. It will be understood that in other embodiments, analog output signals (e.g., from variable pressure keys or variable displacement keys) or signals based on such analog output signals may be additionally or alternatively provided to keyboard controller 121 (e.g., via suitable analog to digital conversion (ADC) circuitry or intervening programmable integrated circuit), where such signals may be similarly processed as described herein for digital output signals 732.

Keyboard controller 121 may also be configured as shown to execute firmware including stored information in the form of an application key map register 704 that is created and/or updated according to application key configuration parameters 320 received from communication API 314. In this embodiment, application key map register 704 translates the list of active application (e.g., game) keys 320 into a list that is indicative of allowed and unallowed keys across the entire keyboard matrix 199. The content of the application key map register 704 may be used in two operations in parallel: 1) it may be used to dictate whether to block or allow a scan code 736 of a particular key assembly from being reported to the OS 354 and 2) it may be used to address a respective EPM 197 or set of EPM's 197 of each key assembly 405 to pulse accordingly to result in either a retraction or extension of the keycap 404 of the respective key assembly 405. In this embodiment, keyboard controller 121 may execute other firmware components such as legacy scan lookup table 708, mask 710, and final scan code output 711 that together operate to produce the final scan code signals 736 reported to the OS only for those allowed key/s 404 currently specified by a current list 761 of allowed key assemblies 405 that is provided from application key map register 704. In this regard, digital output signals 732 exiting the key matrix 199 may be first provided to legacy scan code lookup table 708 to output scan code signals 763 corresponding to each of currently-depressed key assemblies 405 to a key mask 710. The key mask 710 operates to block scan codes 736 from unallowed key assemblies 405 from being reported to the OS 354 via the keyboard device driver 316, as well as allowing scan codes 736 from allowed key assemblies 405 to be reported to the OS 354 via the keyboard device driver 316. Final scan code output 711 then outputs final scan code signals 736 corresponding to only the currently-allowed keys identified by allowed key assembly list 761 to device driver 316 executing on host programmable integrated circuit 105. Further information on production of scan codes based on digital output signals received from keys (key assemblies) of a keyboard matrix may be found in U.S. Pat. No. 8,700,829, which is incorporated herein by reference in its entirety for all purposes.

Keyboard controller 121 is also configured in this embodiment to implement EPM matrix control and addressing 706 based on the same list of currently allowed key/s 761 described above that is provided from application key map register 704. In particular, EPM matrix control and addressing 706 may output general purpose input/output signals as addressed key assembly control signals 734 corresponding to currently-allowed keys identified by allowed key assembly list 761 to decode and driver circuitry 195 (e.g., half H-bridge drivers or other suitable drivers), which in turn provides individual current pulses 450 to selected EPMs 197 to cause retraction and/or extension of those keycaps 404 of individual key assemblies 405 as specified by the list of currently-allowed key/s 761 (e.g., to extend currently-identified individual key assemblies 405, and to retract any individual key assemblies 405 that are not currently identified as allowed). Alternatively or additionally, keyboard MCU 121 may provide addressed key assembly control signals 734 to cause EPM decode and driver circuitry 195 to provide a current pulse to corresponding individually-addressed EPMs 197 to impart a desired peak depression force to only those key assemblies 405 of keyboard matrix 199 that are designated by the current instance of the user-configurable key map information within the application key configuration parameters 320 of keyboard MCU 121 based on information contained in allowed key assembly list 761. It will be understood that the allowed key assembly list 761 may be updated in real time according to key retraction profile configurator application 310, e.g., according to change in identity of the application 312 currently in focus and according to user-input changes to the identity of keys to be retracted for the current application 312 in focus via the user configured or modified key map file 311. The allowed key assembly list 761 may also be updated in real time according to key retraction and extension commands provided directly by the application 312 as updated key map information across direct communication path 771 (without being provided to key retraction profile configurator application 310) to API 314, and then from API 314 via USB as application key configuration parameters 320 that include the updated application key map information that is provided in real time to the application key map register 704 of keyboard MCU 121.

When a given user application 312 of FIG. 7 goes into focus, key retraction profile configurator application 310 accepts an application key map file 770 provided as default key settings from the currently in-focus application 312 (e.g., such as computer game, word processing application, spreadsheet application, media player application, web browser application, etc.). The provided application key map file 770 may include a default list of the designated keyboard key assemblies 405 that are to be used by the particular application 312 that is currently in focus. It will be understood that key retraction profile configurator application 310 may access such a list of key assemblies 405 in any other suitable manner, e.g., such as stored in a lookup table of designated key assemblies 405 for different user applications 312 that are maintained on system storage 135, NVM 107, etc. As shown in FIG. 7, key retraction profile configurator application 310 may be configured to allow a user 796 to optionally modify or change the default key settings for an in-focus user application 312, including the particular combination of key assemblies 405 designated for the application 312 (and/or peak depression force of individual key assemblies designated for the application 312) by its application key map file 770, lookup table, etc.

In some embodiments, key retraction profile configurator application 310 may be used when a particular user application 312 has not been designed or otherwise configured to support the communication API 314. In this regard, a user has the ability to use the key retraction profile configurator application 310 to define their own configuration of key assemblies 405 to be used by the application 312 so that upon launch of the application 312, the key assemblies 405 used by the application 312 are placed in extended and operable position 210 while all other key assemblies 405 not used by the application 312 are placed in the retracted (non-operable) position 211, in a manner described elsewhere herein.

In one embodiment, user configurable key map information 311 may only define or instruct the extended and/or retracted positions for each of the key assemblies 405 that is to be implemented upon launch of the application 312, after which each of the key assemblies 405 stays in its defined extended or retracted position until closure of the application 312, at which time all retracted key assemblies 405 may be returned to extended position 210 and operable mode while all extended key assemblies may be maintained in extended position 210 and operable mode. In a further embodiment an executing user application 312 may utilize direct communication path 771 to communicate to the keyboard MCU 121 the identity of key assemblies 405 to be placed in operable extended position 210 upon launch of user application 312, as well as to communicate identity of single or multiple key assemblies 405 to be extended and/or retracted in real-time while user application 312 is executing on host programmable integrated circuit 105 and receiving input from a user via depression of operable and extended key assemblies 405. In the latter case, a user application 312 may be designed by its developer to support the communications API 314 to write updated key map information transmitted by direct communication path 771 and API 314 to cause keyboard MCU 121 to control key assembly extension and retraction due to occurrence of in-application events, changes in application or key status, resource status, etc.

Examples of types of user modifications to default key settings include, but are not limited to, inclusion of the keys (key assemblies 405) required for a user to type in their Windows password (e.g., especially if they are not used in the designated active application 312), changes to the identity of designated key assemblies 405, creation of a user's own custom list of designated key assemblies 405 assigned to a given user application 312, creation or modification of designated macro key assemblies 405 for use with the in-focus application 312, reassignment of keyboard key assemblies 405 to different application functions, creation of macros assigned to given key assemblies 405, etc. Input 797 from user 796 may be received, for example, via input from integrated keyboard and touchpad 145 to a GUI of display 125, or using any other suitable input/output device. A user 796 may also download (e.g., from social sharing) a list of designated key assemblies 405 assigned to a given user application 312.

After receiving key settings from the currently in-focus application 312 and accepting any user modifications or changes, configurator application 310 then passes the resulting user-configurable application key map file 311 (list of together with any user modifications or changes) to keyboard controller 121 via communication API 314 as application key configuration parameters 320. Keyboard controller 121 accepts the provided application key configuration parameters 320 (including application key map file 311) and creates an application key map register 704 in firmware that identifies both the list of allowed key assemblies 405 and/or peak depression force for key assemblies 405 designated to be used by the application 312 currently in focus, together with any additional allowed key assemblies 405 added by user configuration input 797 as well as identification and designation of all non-allowed keys (i.e., in this embodiment all keyboard keys not found in the key map file 311).

In one embodiment further described below, under the control of keyboard controller 121, key assemblies 405 designated as allowed by application key map register 704 will be the only key assemblies extended and rendered capable of functioning and outputting final (or filtered) scan code signals 736 to OS layer 354 via final scan code output 711. All other non-designated key assemblies 405 will have their scan codes 763 blocked by the mask 710 so they are not reported to the OS layer 354, and will be retracted out of position and rendered not capable of accepting user input by EPM matrix control/addressing firmware 706 implemented by keyboard controller 121. In particular, EPM matrix control/addressing 706 individually addresses the EPM or EPMs 197 of each key assembly 405 of the keyboard matrix 199, and dictates whether to cause decode and bridge driver circuitry 195 to apply appropriate current pulse/s 450 to each given key assembly 405, e.g., to magnetize a respective EPM 197, to de-magnetize a respective EPM 197, to cause a particular peak depression force, or to reverse polarity of magnetic field of a respective EPM 197 so as to retract or extend each given key assembly 405 according to the current application key map register 704 for the application 312 in focus. It will be understood that appropriate types and number of current pulses 450 required to retract and extend the keycap 404 and/or vary peak depression force will depend on specific configuration of each given key assembly 405 and/or specified peak depression force, e.g., such as the different configurations described and illustrated in relation to FIGS. 4A-6D.

EPM matrix control/addressing firmware 706 of keyboard controller 121 may be configured to cycle through addressing (writing) to the EPM/s 197 of each key assembly 405 in a matrixing or matrix type method by addressing the EPM/s 197 of one row and column intersection at a time (e.g., while the EPM/s 197 at all other row and column intersections are tri-stated or otherwise placed out of circuit). In an alternative embodiment, EPMs 107 of multiple key assemblies 405 may be independently addressed at the same time to reduce the amount of time required to program all EPMs 107 of keyboard matrix 199. In any case, general purpose input/output (GPIO) output signals may be provided under the control of EPM matrix control/addressing firmware 706 to decode and bridge driver circuitry 195, which in turn provides corresponding current pulses 450 to EPMs 197 of particular key assemblies 405 specified by EPM matrix control/addressing firmware 706 to cause retraction or extension of, and/or to set or vary peak depression force for, key assemblies 405 designated by application key map register 704.

Still referring to keyboard controller 121 of FIG. 7, scan code reporting to OS layer 354 may also optionally be controlled based on the currently designated key assemblies 405 of application key map register 704 using mask 710 and final scan code output 711 firmware components. For example, when a given user application 312 is in focus and a corresponding application key map register 704 of corresponding designated key assemblies 405 has been created as previously described, initial scan code signals 763 corresponding to all key assemblies 405 not listed as allowed by current list 761 are filtered out by mask 710 and not passed to final scan code output 711 so as to block these filtered scan codes from being provided to OS layer 354 that correspond to any digital output signals 732 received from such non-allowed key assemblies 405. For example, if a given user application 312 (e.g., computer game) together with any user input 797 designates only a portion of the key assemblies 405 of a keyboard matrix 199 (e.g., designates 15 key assemblies 405 out of 107 available key assemblies of a QWERTY keyboard), these designated allowed keys 405 are reported by list 761 to mask 710 which then blocks reporting of scan codes from all other non-designated (i.e., non-allowed) keyboard assemblies 405 to keyboard driver 316 of OS layer 354.

In one embodiment, whenever no user application 312 is in focus and/or no application key map file 770 has been provided to key retraction profile configurator application 310, an “all keys active” mode keyboard state may be implemented. This may be implemented as part of the reset firmware in the keyboard controller 121 such that upon boot-up, the keyboard MCU 121 initializes, and part of the initialization is setting the application key map 704 such that all keys are designated as “allowed keys” and passed to the mask 710 and to EPM matrix control/addressing 706. When this is done, scan codes 736 from 100% (or all) of the keyboard key assemblies 405 are accepted (not blocked), and EPM matrix/control addressing 706 runs through a sequence of programming of EPM(s) 197 of each respective key assembly 405 so that all key assemblies 405 are placed in an extended state.

In an another possible embodiment, whenever no user application 312 is in focus and/or no application key map file 770 has been provided to key retraction profile configurator application 310, key retraction profile configurator application 310 may provide an application key map file 311 to keyboard controller 121 via communication API 314 as application key configuration parameters 320 that designate all key assemblies 405 of keyboard matrix as allowed key assemblies, e.g., with a default peak depression force in those embodiments where variable peak depression force is enabled. In this case, the list 761 of allowed key assemblies provided to EPM matrix control/addressing firmware 706 and mask 710 will include all key assemblies 405. In response, EPM matrix control/addressing firmware 706 will control extension of all keyboard assemblies 405 by their respective EPMs 197, and mask 710 will enable scan codes to from all keyboard assemblies 405 to be passed to keyboard driver 316 of OS layer 354. Whenever a user application 312 is again in focus, then application key map register 704 will again be updated via application key configuration parameters 320 to include only a subset of all available keys of keyboard matrix 199, and/or the specified peak key depression force/s for the key assemblies 405 specified for their user application 312 in focus. In this case, the list 761 of allowed key assemblies provided to EPM matrix control/addressing firmware 706 and mask 710 will include only the subset of designated allowed key assemblies 405. In response, EPM matrix control/addressing firmware 706 will control extension and/or peak depression force of only those designated keyboard assemblies 405 by their respective EPMs 197, and mask 710 will enable scan codes from only those designated keyboard assemblies 405 to be passed to keyboard driver 316 of OS layer 354. Similar real time update of allowable key assemblies 405 may be performed whenever application key map register 704 is updated with a different combination of designated allowed key assemblies 405 via application key configuration parameters 320, e.g., such as whenever the identity of an in-focus user application 312 changes and/or whenever a user inputs changes to the identity of the keys designated for an in-focus application 312. After the user application 312 is no longer in focus, EPM matrix control/addressing firmware 706 may once again control extension of all keyboard assemblies 405 by their respective EPMs 197, and mask 710 will enable scan codes to from all keyboard assemblies 405 to be passed to keyboard driver 316 of OS layer 354, e.g., until another user application 312 is in focus.

FIG. 8 illustrates one exemplary embodiment of circuitry including a single keyboard controller 121 that is configured to implement digital keyboard scan code and filtering 708/710 for an information handling system 100, together with one or more other optional features such as EPM key assembly retraction control 706, N-key rollover 812 (i.e., the ability to report all scan codes of all key assemblies 405 that are pressed down simultaneously at any given time), lighting control 802 and variable pressure sensing/reporting control 804, etc. In this regard, FIG. 8 illustrates exemplary N-key rollover output signals 828 provided from keyboard controller 121, variable pressure scan code output signals 820 supplied from keyboard controller 121, as well as lighting control output signals 880 that may be supplied from keyboard controller 121, e.g., to light drivers 122 that respond by providing current 882 for driving LEDs or other type light elements 252. Examples of lighting control 802 tasks are described in U.S. Pat. No. 7,772,987, and examples of variable pressure sensing and reporting control may be found in U.S. Pat. No. 8,700,829, each of which is incorporated herein by reference in its entirety. Specific examples of programmable integrated circuits that may be employed for keyboard controller 121 include, but are not limited to, a Holtek part number HT32F1654 MCU based on an ARM Cortex M3 core and available from Holtek Semiconductor of Taiwan.

Still referring to FIG. 8, EPM retraction control 706 may in one exemplary embodiment be implemented by firmware of keyboard controller 121 to output key assembly signals 734 to decode and bridge driver circuitry 195 to address and control the EPM/s 197 of each individual key assembly 197 one at a time to retract or extend its respective keycap 404 while the EPMs 197 of all other key assemblies 405 of the keyboard matrix 199 are tri-stated, e.g., by providing individual key assembly control signals 734 from keyboard controller 121 to line decoders 830 in a round robin fashion. Line decoders 830 may in turn provide corresponding chip select signals 890 to driver circuitry 832 (e.g., ½ H-bridge drivers) to cause driver circuitry 832 to supply separate current pulses 450 to the EPM/s 197 of one key assembly 405 at time to impart mechanical retraction or extension action 451 to its corresponding keycap 404. It will be understood that in other embodiments, it is possible to control driver circuitry 832 to simultaneously retract or extend keycaps 404 of more than one key assembly 405 at a time, e.g., such as of all key assemblies of a keyboard matrix 199.

It will be understood that in other embodiments, multiple programmable integrated circuits may be employed to implement features such as EPM retraction control 706, N-key rollover 812, lighting control 802 and variable pressure sensing/reporting control 804. For example, in one exemplary embodiment, three separate MCUs may be provided to individually control each of respective legacy scan lookup table 708 and/or filtering 710, EPM retraction control 706, and lighting control 802. In another possible embodiment, a single MCU may be employed to controls all three of legacy scan lookup table 708 and/or filtering 710, EPM retraction control 706, and lighting control 802 to reduce utilized printed circuit board (PCB) area. In such an embodiment, EPM retraction control 706 is located in the same chip that processes the scan codes, and has sufficient GPIO pins as required by EPM addressing and control of EPM retraction control 706. In another possible embodiment, a first MCU may be employed to implement legacy scan lookup table 708 and/or filtering 710, and a second and different MCU employed to implement EPM retraction control 706 and lighting control 802. Such an embodiment may be employed, for example, for key assemblies of peripheral input devices (e.g., such as mice or game controllers) that do not have a keyboard matrix array. This also makes possible a single USB port for providing both lighting and EPM commands via a single API 314 to a single MCU that implements both EPM retraction control 706 and lighting control 802.

FIGS. 9A-9C illustrate an exemplary embodiment of circuit components 900 that include keyboard controller 121, decode circuitry 830, driver circuitry 832 and EPMs 197 of key assemblies 405, and an optional non-EPM driven Mode Toggle Key or button 200, as they may be coupled together according to one exemplary embodiment. In this embodiment, bi-directional current drive is employed using half H-bridge drivers 832 in a matrixing scheme, and one EPM 197 at a time is programmed with a respective current pulse 450. Any suitable programmable integrated circuit and driver circuitry components may be employed, however in one exemplary embodiment keyboard controller 121 may be a Holtek HT32F1654 ARM Cortex M3 controller, decode circuitry 830 a may be a 4-to-16 line decoder with non-inverting outputs (e.g., such as a NXP 74HCT4514), decode circuitry 830 b may be a 3-to-8 line decoder with non-inverting outputs (e.g., such as a NXP 74HCT238), and ½-H-Bridge drivers 832 a and 832 b may be, for example, implemented using multiple Texas Instruments TI DRV8844 driver chips (each of which has Quad ½ H-Bridge drivers in one integrated circuit).

In the illustrated embodiment of FIGS. 9A-9C, keyboard controller 121 and decode circuitry 830 components are coupled to receive power from low voltage supply rail V_(L) 995 (e.g., 3.5 volts or any other suitable voltage for powering keyboard controller 121 and decode circuitry 830), while driver components 832 are coupled to receive power from high voltage supply rail V_(H) 997 (e.g., 40 volts or any other suitable voltage for driving EPMs 197). As illustrated, EPM matrix control and addressing 706 of this embodiment may output key assembly control signals 734 that include row control signals 960 for selecting a row of EPMs 197, column control signals 970 for selecting a column of EPMs 197, and fault sensing signals 980.

Row control signals 960 include row address signals 964 that are provided to row decoder circuit 830 a for selecting a single row of EPMs 197 that includes a given key assembly 405 of interest selected in a given current pulse cycle. In this embodiment, row decoder circuit 830 a is illustrated as a 4 to 16 binary non-inverting decoder for selecting one row among sixteen rows of EPMs 197 however more or less row decoder output signals may be used depending on the number of rows of keys in a given keyboard matrix 199. Row control signals 960 also include row decode enable signal 966 that that is provided to row decoder circuit 830 a to force all decoder 830 a outputs to an inactive state, such as after all EPM's 197 of key assemblies 405 have been programmed into their desired extended or retracted states. Row control signals 960 also include “Row In” signal 962 that is provided to each of individual ½-H bridge row drivers 832 a to control direction of the current pulse 450 of the present current pulse cycle. Amplitude of a given current pulse may be controlled, for example, by a using pulse width modulated (PWM) signal during the current pulse to control the current pulse amplitude or by using any other suitable current control technique and/or circuitry. Column control signals 970 include column address signals 974 that are provided to column decoder circuit 830 b for selecting a single column of EPM's 197 that includes a given key assembly 405 of interest selected in a given current pulse cycle. In this embodiment, column decoder circuit 830 b is illustrated as a 3 to 8 binary decoder for selecting one column among eight columns of keys, however more or less column decoder output signals may be used depending on the number of columns of keys in a given keyboard. Column control signals 970 also include column decode enable signal 976 that that is provided to column decoder circuit 830 b to force all decoder 830 b outputs to an inactive state, such as after all EPM's 197 of key assemblies 405 have been programmed into their desired extended or retracted states. Column control signals 970 also include “Column In” signal 972 that is provided to each of individual ½-H bridge column drivers 832 b to control direction of the current pulse 450 of the present current pulse cycle.

Also illustrated in FIGS. 9A-9C are optional fault sensing signals 980 that include row driver fault signal 982 that may be provided to keyboard controller 121 from row fault AND gate 935 a when a driver fault (e.g., such as over-current, short circuit, under-voltage, over-temperature, etc. condition) is indicated by any of ½-H bridge row drivers 832 a via its respective fault output signal 999 a, and column driver fault 984 signal that may be provided to keyboard controller 121 from column fault AND gate 935 b when a driver fault is indicated by any of ½-H bridge column drivers 832 b via its fault output signal 999 b. In one embodiment, fault AND gates 935 a and 935 b output high driver fault signals 982 and 984 to keyboard controller 121, respectively, to indicate normal operation as long as all of the respective coupled ½-H bridge drivers 832 all provide “high” inactive fault output signals 999 to the respective fault AND gates 935 a and 935 b during normal driver operation. In such an embodiment, a fault is indicated by any one or more of ½-H bridge drivers 832 by outputting a “low” fault output signal 999 to its respective fault AND gate 935 a or 935 b, which in turn causes the respective fault AND gate 935 a or 935 b to output a respective “low” driver fault signal 982 or 984 to keyboard controller 121 to indicate a driver fault. Keyboard controller 121 may then respond to a “low” driver fault signal 982 or 984 by taking a fault action such as shutting down, restarting, displaying a GUI message on display 125, etc.

Still referring to FIGS. 9A-9C, sixteen ½ H-bridge row drivers 832 a are provided, each coupled to output/receive a current pulse 405 to/from a row of multiple EPMs 197 that correspond, for example, to one of sixteen keyboard rows of keyboard matrix 199. Similarly, eight ½ H-bridge column drivers 832 b are provided, each coupled to output/receive a current pulse 405 to/from a group of EPMs 197 that correspond to one of the eight keyboard columns of keyboard matrix 199. In this configuration, a current pulse 450 may be passed through any given one of the EPMs 197 that corresponds to the intersection of a given one of the rows of EPMs 197 with a given one of the columns of EPMs 197.

To select one of the rows of EPMs 197 at any given time, row decoder circuit 830 a is coupled as shown to output sixteen different separate chip select signals 915 (with only one active at time) to the respective sixteen different ½ H-bridge row drivers 832 a. To simultaneously select one of the columns of EPMs 197 at the same given time, column decoder circuit 830 b is coupled as shown to output eight different separate chip select signals 917 (with only one active at time) to the respective eight different ½ H-bridge column drivers 832 b. In this regard, row decoder circuit 830 a outputs only one active-high (CS=1) chip select signal 915 to one of the ½ H-bridge row drivers 832 a that corresponds to a given row selected by row address signal 964 received from EPM matrix control/addressing firmware 706, while at the same time maintaining all other chip select signals 915 in an inactive-low state, resulting in their respective ½ H-bridge row drivers 832 a operating in a tri-state condition, so un-powered EPM/s 197 are not increasing the load on the ½ H Bridge driver signal. Simultaneously, column decoder circuit 830 b outputs only one active-high (CS=1) chip select signal 917 to one of the ½ H-bridge column drivers 832 b that corresponds to a given column selected by column address signal 974 received from EPM matrix control/addressing firmware 706, while at the same time maintaining all other chip select signals 917 in an inactive-low state, resulting in their respective ½ H-bridge column drivers 832 b operating in an tri-state condition, so un-powered EPMs 197 do not increase the load on the ½ H Bridge driver signal. Thus, EPM matrix control/addressing firmware 706 may select one of the EPMs 197 at any given time for receiving a current pulse 450 based on a combination of row address signal 964 and column address signal 974. EPM matrix control/addressing firmware 706 may then proceed similarly to provide a current pulse 450 to each of the EPM/s 197 for each of the other key assemblies 405 (e.g., in round robin fashion) to retract and/or extend the different key assemblies 405 of keyboard matrix 199 according to allowed key assembly list 761 from application key map register 704.

As shown in FIGS. 9A-9C, EPM matrix control/addressing firmware 706 may also control a polarity (or current direction) of a given current pulse 450 through the selected EPM 197 using a combination of digital Row In signal 962 value and digital Column In signal 972 value, e.g., current driven from a selected ½ H-bridge row driver 832 a to a selected ½ H-bridge column driver 832 b based on combination of Row In signal 962=1 (for drive) and Column In signal 972=0 (for sink), or current driven from a selected ½ H-bridge column driver 832 b to a selected ½ H-bridge row driver 832 a based on combination of Row In signal 962=0 (for sink) and Column In signal 972=1 (for drive). Table 2 below gives one example of current pulse direction (relative to FIGS. 9A-9C) as a function of the combination of Row In signal value and Column In signal value provided by EPM matrix control/addressing firmware 706, it being understood that other values may be employed.

TABLE 2 Value of Row Value of Column Current Direction In signal 962 In signal 972 (Polarity) 1 0 Downward = from row driver to column driver 0 1 Upward = from column driver to row driver

As previously described in relation to FIGS. 4A-6D, different current direction or polarity of current pulses 450 may be so selected to control the polarity of the magnetic field of one or more EPM/s 197 according to the configuration of the key assembly 405 of which it is a part. It will be understood that the above signal values are exemplary only, and that any other combination of one or more signal values, or different signal types, may be employed that is suitable for selecting a given EPM 197 and controlling current flow direction to the selected EPM 197 may be employed. Moreover it is possible in other embodiments that current pulses 450 may be simultaneously provided to multiple EPMs 197.

FIG. 10 illustrates one exemplary embodiment of retractable key assembly methodology 1000, e.g., as it may be implemented by software and firmware executing on one or more programmable integrated circuit components of information handling system 100 described herein. In this regard, it will be understood that information handling system 100 is only one embodiment of information handling system configuration with which the disclosed systems and methods may be implemented. As shown, methodology 1000 begins in one of steps 1002, 1004, 1010 or 1012 corresponding to one of four operating modes of host programmable integrated circuit 105.

As shown, methodology proceeds to step 1006 where keyboard controller 121 is initialized when host programmable integrated circuit 105 is booted up in step 1002 or when a given in-focus user application 312 executing in application layer 350 is closed or discontinued. Specifically, in step 1006 application key map register 704 is reset or cleared and the EPM matrix control/addressing 706 programs all the EPMs 197 to cause all key assemblies 405 to be extended, and mask 710 reset or cleared so that no scan code signals 763 are blocked. At this time no user application 312 is in focus and/or no application key information 770 is provided from an in-focus user application 312. In step 1008, a user 796 may create, define, download, and/or store application key profile configuration settings file, and this information may be provided as configurable key map information 311 (e.g., as a user configurable application key map file) via API 314 to keyboard controller 121 where it is used to create an application key map register 704 in step 1020. Next, in step 1022, mask 710 is set up to block scan code signals 763 from depressed key assemblies 405 that are not identified as allowed key assemblies 405 so that the scan codes signals 763 received from these non-identified key assemblies 405 will not be reported to device driver 316 of OS layer 354. In step 1024, each EPM 197 is set up and programmed with an appropriate high voltage high current pulse 450 to extend those key assemblies 405 identified by allowed key assembly list 761, and to retract those key assemblies 405 not identified as being allowed by allowed key assembly list 761 before ending in step 1032 with only those allowed key assemblies extended and accepting user input, e.g., until the system 100 enters another mode of steps 1002, 1004, 1010 or 1012.

As further shown in FIG. 10, when a user application 312 is launched and placed in focus in step 1010, default application key information 770 is provided from an in-focus user application 312 to key retraction profile configurator application 310 in step 1016. In step 1018, a user 796 may optionally modify or change the default key settings 770 for the in-focus user application 312, e.g., such as the particular combination of key assemblies 405 designated for use with the application 312. Methodology 1000 may then proceed to steps 1020-1032 which operate as previously described.

In step 1012, a mode is described which may be implemented in one embodiment to provide the ability for the user to press non-EPM driven Mode Toggle Key or Button 200 which is a designated physical key or button to toggle between a mode where all keys of keyboard matrix 199 are allowed (i.e., all keyboard key assemblies 405 are in extended position 210 and all their scan codes 736 are reported to the OS 354) and the most previous application key map register 704 that was formerly in effect (e.g., in which some of the keyboard key assemblies 405 are non-allowed in retracted position 211 with their scan codes 736 blocked from reporting to OS 354). In one embodiment, step 1012, prior to the user pressing the non-EPM driven Mode Toggle Key or button 200 (or alternatively, an assigned macro key assembly of keyboard matrix 199), the keyboard MCU 121 may be configured to always store a copy of the contents of the application key map register 704 currently in effect in step 1026. When the user presses non-EPM driven Mode Toggle Key or button 200 (or alternatively, an assigned macro key assembly of keyboard matrix 199) in step 1028, methodology 1000 moves to step 1030 where a reset is performed to the application key map register 704 and mask 710. All of the EPMs 197 are then programmed to move or retain all key assemblies 405 into extended position 210, and all scan codes 736 are allowed to exit the final scan code output 711 and be reported to OS layer 354 via keyboard device drivers 316. Once it is determined that the user has pressed the non-EPM driven Mode Toggle Key or button 200 (or alternatively, an assigned always-extended macro key assembly 405 of keyboard matrix 199) again in step 1034, the stored copy of the former contents of the application key map register 704 is reloaded, sent to the mask 710 to immediately start blocking unallowed keys and to reprogram the EPMs 197 to move all unallowed key assemblies 405 back into retracted position 211 in step 1036. This cycle may be continually repeated as the user continues to press the non-EPM driven Mode Toggle Key or button 200 (or alternatively, an assigned always-extended macro key assembly 405 of keyboard matrix 199) to allow the user to endlessly switch from reset of all key assemblies 405 of the entire keyboard matrix 199 to functional condition, back to application key map register 704 in effect, and vice-versa.

As an example implementation of one embodiment of step 1012, a user may be playing an in-focus multi-player game application 312 with keycaps 404 of a first (allowed) portion of key assemblies 405 of keyboard matrix 199 in extended position 210, and with keycaps 404 of a second (unallowed) portion of key assemblies 405 of keyboard matrix 199 in retracted position 211. While so playing the multi-player game application 312, the user may desire to temporarily text chat with other players online. To temporarily facilitate user text entry via any of key assemblies 405, the user may press the non-EPM driven Mode Toggle Key or button 200 (or alternatively, an assigned always-extended macro key assembly 405 of keyboard matrix 199) once to cause all currently-retracted keycaps 404 of key assemblies 405 to move upward to extended position 210, and to cause all currently-extended keycaps 404 of key assemblies 405 to remain in extended position 210, i.e., so that the user can use all key assemblies of keyboard matrix 199 to type whatever text is desired. Then, if the user presses the non-EPM driven Mode Toggle Key or button 200 (or alternatively, an assigned always-extended macro key assembly 405 of keyboard matrix 199) again (e.g., such as upon completion of the text chat session with fellow online gamers), the most previous former application key map register 704 for the currently in-focus multi-player game application 312 (i.e., which has been stored or saved in memory) is recalled and goes into effect immediately, resulting in the retraction of keycaps 404 of unallowed key assemblies 405 and blocking of scan codes 736 of these unallowed key assemblies 405 as dictated by the application's application key map register 704. In another example implementation, a user may also employ this feature of step 1012 to press the non-EPM driven Mode Toggle Key or button 200 (or alternatively, an assigned always-extended macro key assembly 405 of keyboard matrix 199) to login at a Windows login screen or to resume from a sleep mode (e.g., sleeping power state S3 or hibernation power state S4) should an application key map register 704 be currently in effect which otherwise would cause retraction of key assemblies 405 that are required for the user to enter the necessary text to login.

FIG. 11 illustrates another exemplary embodiment of a mode 5 of a retractable key assembly methodology 1100, e.g., as it may be implemented by software and firmware executing on one or more programmable integrated circuit components of information handling system 100 described herein or with any other suitable information handling system configuration.

As shown in FIG. 11, methodology 1100 may start in step 1102 where no user application 312 is in focus and/or no application key information 770 is provided from an in-focus user application 312. In step 1104, a user 796 may use key retraction profile configurator application 310 to create, define, download, and/or store an application key profile configuration settings file for and associated with any given user application 312. Such an application key profile configuration settings file may be created for both applications 312 that support the communications API 314 and that do not support the communications API 314. The user 796 may associate the application key profile configuration settings file with the particular given application 312 such that upon launch of the application, the file is written via the communication API 314 directly to the keyboard MCU 121. This user-created application key profile configuration settings file may also associated with the given user application 312 and stored in system storage 135 (e.g., non-volatile memory such as a hard drive, solid state drive “SSD”, Flash memory, etc.).

In step 1106 a user application 312 is launched which has a user-created application key profile configuration settings file associated with it that was created in step 1104. At the start of step 1008, the user has already created an application configuration settings file for the particular application. Upon launch of the particular application 312, the user-created application key profile configuration settings file associated with the launched application 312 is automatically written from system storage 135 as configurable key map information 311 (e.g., as a user configurable application key map file) via API 314 and USB to keyboard controller 121 where it is used to create an application key map register 704. Methodology 1100 may then proceed from step 1108 of FIG. 11 to step 1022 of FIG. 10. Note that in one embodiment, upon closure of the application 312, keyboard MCU 121 may re-initialize and return all the key assemblies 405 to the extended position state 210 and allow all scan codes 736 to be reported to device driver 316 of OS layer 354, resulting in all key assemblies 405 of the keyboard being functional (operational and available) again. This step may be implemented for any of the operational modes herein upon closure of an executing application 312 where only a portion of the keyboard assemblies 405 have previously been extended and available for the executing application.

FIG. 12 illustrates another exemplary embodiment of a mode 6 of a retractable key assembly methodology 1200 that may be implemented to support the launch of a particular application 312 which has been developed to support the communications API 314 with retraction and extension commands written directly from the user application 312. Methodology 1200 may be implemented, for example, by software and firmware executing on one or more programmable integrated circuit components of information handling system 100 described herein or with any other suitable information handling system configuration.

As shown in FIG. 12, methodology 1200 may start in step 1202 where no user application 312 is launched and in focus. Upon launch of the user application 312 in step 1204, the application 312 writes the key map file via direct communications path 771 and API 314 and USB as application key configuration parameters 320 to keyboard controller 121 where it is used to create application a key map register 704 of the MCU 121 in a manner as described elsewhere herein. Methodology 1200 may then proceed from step 1206 of FIG. 12 to step 1022 of FIG. 10. After execution of steps 1022 and 1024 of FIG. 10, the keyboard is now in a state where the key assemblies 405 have been retracted and/or extended upon launch of the application 312 according to the information in the key map register 704, and in a further optional embodiment the keyboard MCU 121 is now listening for the application 312 (which supports the communications API 314) to provide real-time extension and retraction commands as updated key configuration parameters via API 314 for any one or more key assemblies 405, e.g., as further described in relation to FIG. 13.

FIG. 13 illustrates another exemplary embodiment of a mode 7 of a retractable key assembly methodology 1300 that may be implemented to support a particular launched application 312 which has been developed to support the communications API 314 with real time in-application retraction and extension commands for any one or more key assemblies 405 written directly from the user application 312 to the communications API 314. In one embodiment, communications API 314 may be programmed to recognize that launched application 312 supports real time in-application retraction and extension commands based on an application identifier (e.g., manufacturer application identification number, application serial number, etc.) provided from application 312 to communications API 314 and, when so, to implement methodology 1300. Methodology 1300 may be implemented, for example, by software and firmware executing on one or more programmable integrated circuit components of information handling system 100 described herein or with any other suitable information handling system configuration.

FIG. 13 starts in step 1302 and 1304 with a user application 312 launched and in focus, e.g., such as upon completion of the methodology 1200 of FIG. 12, including step 1024 of FIG. 10. In step 1306, the application 312 monitors the real time availability of at least one resource or ability of the executing user application 312 that is associated with at least one given one of the key assemblies 405 and instructs the keyboard MCU 121 to retract or extend any single key assembly 405 or set of key assemblies 405 according to this monitored availability of the resource or ability by providing real time updated key map information via direct communication path 771 to API 314 and USB as updated application key configuration parameters 320 to keyboard MCU 121. This real time updated key map information may include a key map file update of reduced size (i.e., smaller than a complete key map file for the key assemblies 405 of the entire keyboard matrix 199), only containing updated retracted/extended position information for one or more particular key assemblies 405, i.e., only for those key assemblies 405 that are currently being updated from extended position 210 to retracted position 211 (or vice-versa), and not for any key assemblies 405 that being changed in retracted/extended position in the current iteration. In step 1308, the real time updated key assembly positions for only those affected one or more key assemblies 405 may be written in the application key map register 704 of the keyboard MCU 121. In step 1310, the updated allowed key assembly list 761 of this iteration (including updated allowed key assembly positions 405 of this iteration that are now in the application key map register 704) is written to mask 710, which is set up to block scan code signal 763 from any user-depressed key assembly 405 that is not identified as an allowed key assembly 405 in the current list 761 so that the scan code signal 763 received from any newly non-identified (non-allowed) key assembly 405 of this iteration will not be reported to device driver 316 of OS layer 354 in a manner similar to step 1022 of FIG. 10.

Still referring to FIG. 13, in step 1312 the updated allowed key assembly list 761 of this iteration (including updated allowed key assembly positions 405 of this iteration that are now in the application key map register 704) is written to EPM matrix control/addressing 706, and the EPM 197 of each key assembly 405 that has been updated in position (i.e., updated from retracted position 211 to extended position 210 in key map register 704, or from extended position 210 to retracted position 211 in key map register 704) is set up and programmed with an appropriate current pulse 450 to extend its respective key assembly 405 identified by allowed key assembly list 761, or to retract the key assembly 405 if not identified as being allowed by allowed key assembly list 761 in a manner similar to step 1024 of FIG. 10. The result of step 1312 is that only the allowed key assemblies 405 of this iteration are extended and accepting user input as available and operable key assemblies 405.

As long as the current application 312 is in-focus and active (executing) in step 1314, then methodology 1300 may return to step 1306 and steps 1306-1312 may iteratively repeat such that the current application 312 continues to instruct additional key assemblies 405 to move from extended position 210 to retracted position 2100 (or vice versa) in real time, e.g., such as upon occurrence of in-application events or status (e.g., resource status). Thus, by iteratively repeating steps 1306 to 1312 of methodology 1300, an executing in-focus user application 312 (which has been developed to support the communications API 314), may support in-application real-time API commands to extend or retract any single key assembly 405 or group of multiple key assemblies 405 due to application occurrences (such as in-application events or status (e.g., resource status)) as many times as the application 312 wishes while the application 312 is running. Steps 1306-1312 of methodology 1300 may iteratively repeat at any suitable rate for a given implementation, and in one embodiment may iteratively repeat at a rate of at least one time per second, alternatively at least five times per second, alternatively at least 10 times per second, alternatively from one time per second to 30 times per second, alternatively from about one time per second to about 20 times per second, alternatively from about one time per second to about 10 times per second, and further alternatively from about 10 times per second to about 20 times per second. However iteration rates of less than one time per second and more than 30 times per second are also possible.

If application 312 is found to no longer be active and in-focus in step 1314 (e.g., upon closure of application 312), then methodology 1300 proceeds to step 1006 of FIG. 10, i.e., keyboard MCU 121 is re-initialized to extend all key assemblies 405 to extended position 210 and to clear mask 710 to allow scan codes 736 from all key assemblies to be reported to the device driver 316 of OS layer 354, resulting in all key assemblies 405 of the keyboard being functional (operational and available) again. It will be understood that in one alternative embodiment, the above methodology may terminate after step 1006 with all key assemblies 405 extended and operational for accepting user input, i.e., without performing steps 1008-1024 of FIG. 10 which may be skipped in this alternative embodiment.

It will be understood that the methodologies of each of FIGS. 10-13 are exemplary only, and that any other combination of fewer, additional, and/or alternative steps may be performed to control selectable retraction and extension of key assemblies 405 and/or to control transmission of scan codes from key assemblies 405 or any other suitable key input device.

It will also be understood that in one embodiment, magnetically permeable materials employed herein (e.g., as shunts, plate, levers, etc.) may be selected to be magnetically “soft” materials, meaning that these materials become magnetic when a magnetic field is present but will relatively quickly become unmagnetized when the external field is removed. In one embodiment, permanent magnet materials employed herein (e.g., for EPM components, attached to angled support arms, etc.) may be selected to be magnetically “hard” materials, meaning that these materials require relatively very strong magnetic fields to magnetize but they will hold that magnetization after the external field is removed.

It will also be understood that one or more of the tasks, functions, or methodologies described herein for an information handling system or component thereof (e.g., including those described herein for components 103, 105, 110, 111, 120, 121, 123, etc.) may be implemented by circuitry and/or by a computer program of instructions (e.g., computer readable code such as firmware code or software code) embodied in a non-transitory tangible computer readable medium (e.g., optical disk, magnetic disk, non-volatile memory device, etc.), in which the computer program comprising instructions are configured when executed on a programmable integrated circuit (e.g., processor such as CPU, controller, microcontroller, microprocessor, ASIC, etc. or programmable logic device “PLD” such as FPGA, complex programmable logic device “CPLD”, etc.) to perform one or more steps of the methodologies disclosed herein. In one embodiment, such programmable integrated circuits may be selected from the group consisting of CPU, controller, microcontroller, microprocessor, FPGA, CPLD and ASIC. The computer program of instructions may include an ordered listing of executable instructions for implementing logical functions in an information handling system or component thereof. The executable instructions may include a plurality of code segments operable to instruct components of an information handling system to perform the methodologies disclosed herein. It will also be understood that one or more steps of the present methodologies may be employed in one or more code segments of the computer program. For example, a code segment executed by the information handling system may include one or more steps of the disclosed methodologies. It will be understood that a programmable integrated circuit may be configured to execute or otherwise be programmed with software, firmware, logic, and/or other program instructions stored in one or more non-transitory tangible computer-readable mediums (e.g., example, data storage devices, flash memories, random access memories, read only memories, programmable memory devices, reprogrammable storage devices, hard drives, floppy disks, DVDs, CD-ROMs, and/or any other tangible data storage mediums) to perform the operations, tasks, functions, or actions described herein for the disclosed embodiments.

For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, calculate, determine, classify, process, transmit, receive, retrieve, originate, switch, store, display, communicate, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, or other purposes. For example, an information handling system may be a personal computer (e.g., desktop or laptop), tablet computer, mobile device (e.g., personal digital assistant (PDA) or smart phone), server (e.g., blade server or rack server), a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include random access memory (RAM), one or more processing resources such as a central processing unit (CPU) or hardware or software control logic, ROM, and/or other types of nonvolatile memory. Additional components of the information handling system may include one or more disk drives, one or more network ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, touch screen and/or a video display. The information handling system may also include one or more buses operable to transmit communications between the various hardware components.

While the invention may be adaptable to various modifications and alternative forms, specific embodiments have been shown by way of example and described herein. However, it should be understood that the invention is not intended to be limited to the particular forms disclosed. Rather, the invention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the appended claims. Moreover, the different aspects of the disclosed systems and methods may be utilized in various combinations and/or independently. Thus the invention is not limited to only those combinations shown herein, but rather may include other combinations. 

What is claimed is:
 1. An information handling system, comprising: at least one programmable integrated circuit programmed to execute an operating system and to execute a given session of a given in-focus user application on the information handling system; one or more depressible key assemblies, each of the key assemblies coupled to provide an output signal when depressed by a user and having an extended position and a retracted position that is selected in response to a control signal; at least one programmable integrated circuit coupled to receive the output signals provided by each of the depressible key assemblies and coupled to provide corresponding input signals to the operating system based on the output signals provided by each of the depressible key assemblies; and at least one programmable integrated circuit coupled to provide the control signal to control a height of at least one given key assembly between the extended position and the retracted position in real time while the same given session of the same given user application continues to execute based on change in a real time availability of at least one ability or resource provided by the given in-focus application that is associated with the given key assembly during execution of the same given session of the given user application; where the at least one programmable integrated circuit is coupled to monitor a temporary availability of the given resource or ability in real time during the same given session of the same given user application, to provide a control signal to vary the height of the at least one given key assembly in real time during the same given session of the same given user application upon a temporary loss in the availability of the given ability or resource of the given user application for a defined time period, and then to provide a control signal to again vary the height of the at least one given key assembly in real time after a gain of the given ability or resource of the given user application after expiration of the defined time period.
 2. The information handling system of claim 1, where at least one programmable integrated circuit of the information handling system is programmed to output scan codes as input signals to the operating system for input to the executing given in-focus user application based on output signals received from each given one of the key assemblies when the given key assembly is in the extended position and by not outputting any scan codes as input signals to the operating system for input to the executing given in-focus user application based on output signals received from each given one of the key assemblies when the given key assembly is in the retracted position.
 3. The information handling system of claim 1, where a first programmable integrated circuit is programmed to execute the operating system and to execute the given in-focus user application on the information handling system; where a second programmable integrated circuit of the information handling system is coupled to receive output signals provided by each of the depressible key assemblies and to respond by outputting scan codes as the input signals to the operating system based on the output signals received from the depressible key assemblies; and where the second programmable integrated circuit of the information handling system is programmed to output scan codes as input signals to the operating system for input to the given in-focus user application based on output signals received from each given one of the key assemblies when the given key assembly is in the extended position and by not outputting any scan codes as input signals to the operating system for input to the given in-focus user application based on output signals received from each given one of the key assemblies when the given key assembly is in the retracted position.
 4. The information handling system of claim 3, where the first programmable integrated circuit is a host programmable integrated circuit; and where the second programmable integrated circuit is a keyboard controller.
 5. The information handling system of claim 1, further comprising: a keyboard matrix that includes multiple depressible key assemblies; a host programmable integrated circuit that is programmed to execute the operating system and the given user application; and a keyboard controller that is coupled between the keyboard matrix and the host programmable integrated circuit, the keyboard controller being programmed to: receive the output signals provided by each of the depressible key assemblies and coupled to provide corresponding input signals as scan codes to the operating system executed by the host programmable integrated circuit based on the output signals provided by each of the depressible key assemblies, and receive key map information from the host programmable integrated circuit while the given session of the given in-focus user application is executing that is indicative of a real time retracted or extended position for at least a given one of the multiple key assemblies based on a real time temporary availability of at least one ability or resource of the given in-focus application that is associated with the given key assembly, and to respond to the received key map information in real time while the same given session of the same given user application continues to execute by providing the control signal to vary the height of the given key assembly back and forth between the extended position and the retracted position while the same given session of the same given user application continues to execute according to the information received from the host programmable integrated circuit.
 6. The information handling system of claim 5, further comprising a portable information handling system chassis enclosure, each of the keyboard matrix, host programmable integrated circuit, and keyboard controller being integrated within the portable information handling system chassis enclosure.
 7. The information handling system of claim 5, where the keyboard controller is further programmed to: output scan codes as input signals to the operating system executed by the host programmable integrated circuit based on the output signals received from the given key assembly while it is in the extended position; and not output any scan codes as input signals to the operating system based on any output signals received from the given key assembly while it is in the retracted position.
 8. The information handling system of claim 5, where the host programmable integrated circuit is programmed to: execute at least one application programming interface (API); execute the given in-focus user application to provide the key map information that is indicative of a real time retracted position or an extended position for the given one of the multiple key assemblies directly from the given user application to the API; and execute the API to provide the key map information to the keyboard controller that is indicative of a real time retracted or extended position for the given one of the multiple key assemblies.
 9. The information handling system of claim 5, where the at least one programmable integrated circuit is coupled to provide a control signal to lower the height of the at least one given key assembly in real time during the same given session of the same given user application upon a temporary loss in the availability of the given ability or resource of the given user application for a defined time period, and then to provide a control signal to raise the height of the at least one given key assembly in real time after a gain of the given ability or resource of the given user application after expiration of the defined time period.
 10. The information handling system of claim 5, where the at least one programmable integrated circuit is coupled to provide a control signal to raise the height of the at least one given key assembly in real time during the same given session of the same given user application upon a temporary gain in the availability of the given ability or resource of the given user application for a defined time period, and then to provide a control signal to lower the height of the at least one given key assembly in real time after a loss of the given ability or resource of the given user application after expiration of the defined time period.
 11. The information handling system of claim 1, further comprising: a keyboard matrix that includes multiple key assemblies; a host programmable integrated circuit that is programmed to execute the operating system and the given user application; and a keyboard controller that is coupled between the keyboard matrix and the host programmable integrated circuit, the keyboard controller being programmed to: receive the output signals provided by each of the depressible key assemblies and coupled to provide corresponding input signals as scan codes to the operating system executed by the host programmable integrated circuit based on the output signals provided by each of the depressible key assemblies, and receive key map information from the host programmable integrated circuit while the given session of the given in-focus user application is executing that is indicative of a real time retracted or extended position for each individual given one of the multiple key assemblies based on a real time temporary availability of at least one ability or resource of the given in-focus application that is associated with the given key assembly, and to respond to the received key map information in real time while the same given session of the same given user application continues to execute by providing the control signal to individually vary a height of each given key assembly back and forth between the extended position and the retracted position while the same given session of the same given user application continues to execute according to the information received from the host programmable integrated circuit.
 12. The information handling system of claim 1, where the at least one programmable integrated circuit of the information handling system is programmed to iteratively repeat the following steps a) and b) for as long as the same given session of the same given user application continues to execute with the given user application in-focus: a) monitor the real time temporary availability of at least one resource or ability of the executing given user application that is associated with at least one given one of the key assemblies; and b) then provide a control signal to vary the height of the given key assembly between the extended position and the retracted position in real time while the same given session of the same given user application continues to execute based on the monitored real time availability of the at least one ability or resource of the given in-focus user application that is associated with the given key assembly.
 13. The information handling system of claim 1, where the given user application comprises a given computer game, and where the at least one programmable integrated circuit is coupled to provide the control signal to control the height of the at least one given key assembly between the extended position and the retracted position in real time while the same given session of the same given computer game continues to execute in-focus based on change in a real time availability of at least one in-game ability or resource provided by the same given in-focus computer game that is associated with the given key assembly during execution of the same given session of the same given computer game.
 14. The information handling system of claim 1, where the given user application comprises a given computer game, and where the at least one programmable integrated circuit is coupled to: provide the control signal to lower the height of at least one given key assembly from the extended position to the retracted position in real time while the same given session of the same given computer game continues to execute in-focus based on loss in a real time availability of an in-game user ability or resource that comprises one of super speed, force field shield, plasma cannon, laser pistol, grenades, bullets, throwing knives, or health provided by the given in-focus computer game that is associated with the given key assembly during execution of the given session of the given computer game; and then provide the control signal to again raise the height of the at least one given key assembly from the retracted position to the extended position in real time while the same given session of the computer game continues to execute based on a gain in the real time availability of the same in-game user ability or resource provided by the given in-focus computer game that is associated with the given key assembly during execution of the given session of the computer game.
 15. A method of operating an information handling system, the method comprising using the at least one programmable integrated circuit of the information handling system to: execute an operating system and to execute a given session of a given in-focus user application on the information handling system; receive output signals from one or more depressible key assemblies when depressed by a user, and provide corresponding input signals to the operating system based on the output signals received from the depressible key assemblies; and provide a control signal to control a height of at least one given one of the key assemblies between the extended position and the retracted position in real time while the same given session of the same given user application continues to execute based on change in a real time availability of at least one ability or resource provided by the given in-focus application that is associated with the given key assembly during execution of the same given session of the given user application; further comprising monitoring a temporary availability of the given resource or ability provided by the given user application in real time during the same given session of the same given user application; providing a control signal to vary the height of the at least one given key assembly in real time during the same given session of the same given user application upon a temporary loss in the availability of the given ability or resource of the given user application for a defined time period; and then providing a control signal to again vary the height of the at least one given key assembly in real time after a gain of the given ability or resource of the given user application after expiration of the defined time period.
 16. The method of claim 15, further comprising using the at least one programmable integrated circuit of the information handling system to output scan codes as input signals to the operating system for input to the executing given in-focus user application based on output signals received from each given one of the key assemblies when the given key assembly is in the extended position and by not outputting any scan codes as input signals to the operating system for input to the executing given in-focus user application based on output signals received from each given one of the key assemblies when the given key assembly is in the retracted position.
 17. The method of claim 15, further comprising: using a first programmable integrated circuit to execute the operating system and to execute the given in-focus user application on the information handling system; using a second programmable integrated circuit of the information handling system to receive output signals provided by each of the depressible key assemblies and to respond by outputting scan codes as the input signals to the operating system based on the output signals received from the depressible key assemblies; and using the second programmable integrated circuit of the information handling system to output scan codes as input signals to the operating system for input to the given in-focus user application based on output signals received from each given one of the key assemblies when the given key assembly is in the extended position and by not outputting any scan codes as input signals to the operating system for input to the given in-focus user application based on output signals received from each given one of the key assemblies when the given key assembly is in the retracted position.
 18. The method of claim 17, where the first programmable integrated circuit is a host programmable integrated circuit; and where the second programmable integrated circuit is a keyboard controller.
 19. The method of claim 15, where at least one programmable integrated circuit of the information handling system is coupled to a keyboard matrix that includes multiple depressible key assemblies; and where the method further comprises: using a host programmable integrated circuit to execute the operating system and the given user application; and using a keyboard controller that is coupled between the keyboard matrix and the host programmable integrated circuit to: receive the output signals provided by each of the depressible key assemblies and provide corresponding input signals as scan codes to the operating system executed by the host programmable integrated circuit based on the output signals provided by each of the depressible key assemblies, and receive key map information from the host programmable integrated circuit while the given session of the given in-focus user application is executing that is indicative of a real time retracted position or an extended position for at least a given one of the multiple key assemblies based on a real time temporary availability of at least one ability or resource of the given in-focus application that is associated with the given key assembly; and respond to the received key map information in real time while the same given session of the same given user application continues to execute by providing the control signal to vary the height of the given key assembly back and forth between the extended position and the retracted position while the same given session of the same given user application continues to execute according to the information received from the host programmable integrated circuit.
 20. The method of claim 19, where each of the keyboard matrix, host programmable integrated circuit, and keyboard controller are integrated components within a portable information handling system chassis enclosure.
 21. The method of claim 19, further comprising using the keyboard controller to: output scan codes as input signals to the operating system executed by the host programmable integrated circuit based on the output signals received from the given key assembly while it is in the extended position; and not output any scan codes as input signals to the operating system based on any output signals received from the given key assembly while it is in the retracted position.
 22. The method of claim 19, further comprising using the host programmable integrated circuit to: execute at least one application programming interface (API); execute the given in-focus user application to provide the key map information that is indicative of a real time retracted position or an extended position for the given one of the multiple key assemblies directly from the given user application to the API; and execute the API to provide the key map information to the keyboard controller that is indicative of a real time retracted or extended position for the given one of the multiple key assemblies to the keyboard controller.
 23. The method of claim 19, further comprising providing a control signal to lower the height of the at least one given key assembly in real time during the same given session of the same given user application upon a temporary loss in the availability of the given ability or resource of the given user application for a defined time period; and then providing a control signal to raise the height of the at least one given key assembly in real time after a gain of the given ability or resource of the given user application after expiration of the defined time period.
 24. The method of claim 19, further comprising providing a control signal to raise the height of the at least one given key assembly in real time during the same given session of the same given user application upon a temporary gain in the availability of the given ability or resource of the given user application for a defined time period; and then providing a control signal to lower the height of the at least one given key assembly in real time after a loss of the given ability or resource of the given user application after expiration of the defined time period.
 25. The method of claim 15, where at least one programmable integrated circuit of the information handling system is coupled to a keyboard matrix that includes multiple depressible key assemblies; and where the method further comprises: using a host programmable integrated circuit of the information handling system to execute the operating system and the given user application; and using a keyboard controller that is coupled between the keyboard matrix and the host programmable integrated circuit to: receive the output signals provided by each of the depressible key assemblies and provide corresponding input signals as scan codes to the operating system executed by the host programmable integrated circuit based on the output signals provided by each of the depressible key assemblies, and receive key map information from the host programmable integrated circuit while the given session of the given in-focus user application is executing that is indicative of a real time retracted position or an extended position for each individual given one of the multiple key assemblies based on a real time temporary availability of at least one ability or resource of the given in-focus application that is associated with the given key assembly; and respond to the received key map information in real time while the same given session of the same given user application continues to execute by providing the control signal to individually vary a height of each given key assembly back and forth between the extended position and the retracted position while the same given session of the same given user application continues to execute according to the information received from the host programmable integrated circuit.
 26. The method of claim 15, further comprising using the at least one programmable integrated circuit of the information handling system to iteratively repeat the following steps a) and b) for as long as the same given session of the same given user application continues to execute with the given user application in focus: a) monitor the real time temporary availability of at least one resource or ability of the executing given user application that is associated with at least one given one of the key assemblies; and b) then provide a control signal to vary the height of the given key assembly between the extended position and the retracted position in real time while the same given session of the same given user application continues to execute based on the monitored real time availability of the at least one ability or resource of the given in-focus user application that is associated with the given key assembly.
 27. The method of claim 15, where the given user application comprises a given computer game, and where the method further comprises providing the control signal to control the height of the at least one given key assembly between the extended position and the retracted position in real time while the same given session of the same given computer game continues to execute in-focus based on change in a real time availability of at least one in-game ability or resource provided by the same given in-focus computer game that is associated with the given key assembly during execution of the same given session of the same given computer game.
 28. The method of claim 15, where the given user application comprises a given computer game, and where the method further comprises: providing the control signal to lower the height of at least one given key assembly from the extended position to the retracted position in real time while the same given session of the same given computer game continues to execute in-focus based on loss in a real time availability of an in-game user ability or resource that comprises one of super speed, force field shield, plasma cannon, laser pistol, grenades, bullets, throwing knives, or health provided by the given in-focus computer game that is associated with the given key assembly during execution of the given session of the given computer game; and then providing the control signal to again raise the height of the at least one given key assembly from the retracted position to the extended position in real time while the same given session of the computer game continues to execute based on a gain in the real time availability of the same in-game user ability or resource provided by the given in-focus computer game that is associated with the given key assembly during execution of the given session of the computer game. 